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

Re: What happens when the repository is bigger than gc.autopacklimit * pack.packSizeLimit?

From
Jeff King <peff@peff.net>
Date
Aug 27, 2014, 19:47 UTC
Message-ID
<20140827194746.GE7561@peff.net>
In-Reply-To
<201408271936.s7RJarOh011358@hobgoblin.ariadne.com>
On Wed, Aug 27, 2014 at 03:36:53PM -0400, Dale R. Worley wrote:
> And it appears from an experiment that this is what happens.  I have a
> repository with pack.packSizeLimit = 99m, and there are 104 pack
> files, and even when "git gc" is done, if I do "git gc --auto", it
> will do git-repack again.

I agree that "gc --auto" could be smarter here, but I have to wonder: why are you setting the packsize limit to 99m in the first place? It is generally much more efficient to place everything in a single pack. There are more delta opportunities, fewer base objects, lookup is faster (we binary search each pack index, but linearly move through the list of indices), and it is required for advanced techniques like bitmaps.

-Peff
Previous: Dale R. WorleyNext: Dale R. Worley
Message 2 of 7 in “What happens when the repository is bigger than gc.autopacklimit * pack.packSizeLimit?”
  1. Dale R. WorleyAug 27, 2014
  2. Jeff KingAug 27, 2014
  3. Dale R. WorleyAug 29, 2014
  4. Jeff KingAug 29, 2014
  5. Dale R. WorleyAug 29, 2014
  6. Junio C HamanoAug 27, 2014
  7. Dale R. WorleyAug 29, 2014

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.