On 12/7/07, Jeff King <peff@xxxxxxxx> wrote: > On Fri, Dec 07, 2007 at 03:07:05PM -0500, Jon Smirl wrote: > > > I noticed two things when doing a repack of the gcc repo. First is > > that the git process is getting to be way too big. Turning off the > > delta caches had minimal impact. Why does the process still grow to > > 4.8GB? > > > > Putting this in perspective, this is a 4.8GB process constructing a > > 330MB file. Something isn't right. Memory leak or inefficient data > > structure? > > Keep in mind that you are trying many different deltas, which are being > held in memory, to find the right one and generate the 330MB file. And > when you multiply that times N threads going at once, _each one_ is > using a bunch of memory. > > As Nico suggested, you could probably drop the memory usage by reducing > the size of the delta cache. Delta cache is disabled -- pack.deltacachelimit = 0 Unless this option is broken? > > -Peff > -- Jon Smirl jonsmirl@xxxxxxxxx - 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
