Re: Large repo and pack.packsizelimit

From: Nicolas Pitre <nico@fluxnic.net>
Date: May 8, 2012, 21:52 UTC
Message-ID: <alpine.LFD.2.02.1205081751011.21030@xanadu.home>
In-Reply-To: <20120508212012.GA20044@sigill.intra.peff.net>

On Tue, 8 May 2012, Jeff King wrote:

Show 18 quoted lines

> On Tue, May 08, 2012 at 05:13:13PM -0400, Nicolas Pitre wrote:
> 
> > > 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.
> > 
> > IMHO this is the wrong fix.  The pack size limit was created to deal 
> > with storage media with limited capacity.  In this case, the repack 
> > process should be told to limit its memory usage, and pack-index should 
> > simply be taught to cope.
> 
> Hmm, you're right. I was thinking it helped to deal with memory
> addressing issues for 32-bit systems, but I guess
> core.packedGitWindowSize should be handling that. IOW, the 10G packfile
> should work just fine for normal access.
> 
> However, the OP did say he got an "out of memory" error during the
> clone. So maybe there is a problem to be fixed in index-pack there.

Was the OOM on the remote side (pack-objects) or on the local side (index-pack) ?

Nicolas