git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] packfile: fix perf regression with many packs

From
Ben Knoble <ben.knoble@gmail.com>
Date
Aug 13, 2026, 11:18 UTC
Message-ID
<2CE87145-D86E-47DF-8761-8FBCFB774C51@gmail.com>
In-Reply-To
<704409ee-0319-7493-cdc9-8cdb0fea1ace@gmx.de>
Show 46 quoted lines
> Le 13 août 2026 à 05:04, Johannes Schindelin <johannes.schindelin@gmx.de> a écrit :
> 
> Hi Ben,
> 
> On Wed, 12 Aug 2026, Ben Knoble wrote:
> 
>>> Le 12 août 2026 à 15:15, Johannes Schindelin via GitGitGadget
>>> <gitgitgadget@gmail.com> a écrit :
>>> 
>>> [...]
>>>   packfile: fix perf regression with many packs
>>> 
>>>   This issue was spotted by a Microsoft Git user with the massive
>>>   amount of packfiles typical of an average, long-running monorepo
>>>   checkout.
>> 
>> As a different kind of intermediate solution, would turning on
>> maintenance for that user’s checkout help? (Not sure that would help CI
>> clone times unless the server repacks, of course.)
> 
> I should have clarified that the issue is a _Scalar_ clone. And
> specifically a _Microsoft Git Scalar_ clone.
> 
> This matters because, for various reasons that I don't want to elaborate
> on because today I'm in need of lifting up my mood, a substantial part of
> Microsoft Git failed to get upstreamed to core Git.
> 
> One of these is the "shared cache repository", i.e. a bare repository that
> is established as an alternate of the actual clone, and into which the
> actual scheduled fetches go. For full details, see
> https://github.com/microsoft/git/commit/55226d12ed36 (scalar: do
> initialize `gvfs.sharedCache`, 2021-05-03).
> 
> Now, maintenance _does_ run, usually, on that shared cache repository
> (being careful not to inadvertently drop objects merely because they're
> unreachable within the shared cache repository). So theoretically, you're
> right that maintenance should help this issue.
> 
> For reasons (which I don't have the time to find out, but I suspect that
> maintenance simply takes too long and does not finish by the time the
> machine is shut down for the day), it is still not exactly rare to find
> setups with five-digit packfile counts. And since we _can_ handle this
> more gracefully, we should ;-)
> 
> Ciao,
> Johannes
Thanks, very informative!
What I actually meant, sorry if I wasn’t clear, is that maintenance seems likely to help the local (à la PS1) case more than the clone. But maybe it will suffer from the same « takes too long » problem, idk.
Previous: Johannes SchindelinNext: Patrick Steinhardt
Message 10 of 24 in “packfile: fix perf regression with many packs”
  1. packfile: fix perf regression with many packsJohannes Schindelin via GitGitGadget, Aug 12, 2026
  2. Junio C HamanoAug 12, 2026
  3. Jeff KingAug 12, 2026
  4. Patrick SteinhardtAug 13, 2026
  5. Johannes SchindelinAug 13, 2026
  6. Jeff KingAug 13, 2026
  7. Johannes SchindelinAug 13, 2026
  8. Ben KnobleAug 12, 2026
  9. Johannes SchindelinAug 13, 2026
  10. Ben KnobleAug 13, 2026
  11. Patrick SteinhardtAug 13, 2026
  12. Johannes SchindelinAug 13, 2026
  13. Patrick SteinhardtAug 13, 2026
  14. Johannes SchindelinAug 13, 2026
  15. Patrick SteinhardtAug 13, 2026
  16. Junio C HamanoAug 13, 2026
  17. Jeff KingAug 13, 2026
  18. Patrick SteinhardtAug 14, 2026
  19. Jeff KingAug 14, 2026
  20. Patrick SteinhardtAug 17, 2026
  21. Jeff KingAug 17, 2026
  22. packfile: fix perf regression with many packsJohannes Schindelin via GitGitGadget, Aug 13, 2026
  23. Patrick SteinhardtAug 14, 2026
  24. Junio C HamanoAug 14, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.