Re: Large repo and pack.packsizelimit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]