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

Re: Large repo and pack.packsizelimit

From
Jeff King <peff@peff.net>
Date
May 8, 2012, 20:31 UTC
Message-ID
<20120508203137.GA15707@sigill.intra.peff.net>
In-Reply-To
<37267143.413194.1336046278583.JavaMail.ngmail@webmail07.arcor-online.net>
On Thu, May 03, 2012 at 01:57:58PM +0200, th.acker66@arcor.de wrote:
Show 8 quoted lines
> I am using MSysgit 1.7.9 on WinXP 32bit and have a very large repo
> (10GB in .git; 20GB in source tree).  I had to set
> pack.packsizelimit=1024MB to prevent "out of memory" during repacking
> in git-gc and everything seemed to work fine.
> 
> When I tried to clone this repo an "out of memory" occured because the
> packs to be transferred by the git protocol are not limited by
> pack.packsizelimit.

Yes, pack-objects respects pack.packsizelimit when creating local packs, but incoming packs from the network (which are processed by index-pack) are not split.

This should be fixed in git. Unfortunately, I don't know that it is as trivial as just splitting the incoming stream; we would also have to make sure that there were no cross-pack deltas in the result.

-Peff
Previous: th.acker66@arcor.deNext: Nicolas Pitre
Message 2 of 10 in “Large repo and pack.packsizelimit”
  1. th.acker66@arcor.deMay 3, 2012
  2. Jeff KingMay 8, 2012
  3. Nicolas PitreMay 8, 2012
  4. Jeff KingMay 8, 2012
  5. Nicolas PitreMay 8, 2012
  6. ThomasMay 9, 2012
  7. Nguyen Thai Ngoc DuyMay 9, 2012
  8. ThomasMay 9, 2012
  9. Junio C HamanoMay 9, 2012
  10. ThomasMay 10, 2012

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.