Re: Something is broken in repack

From: David Brown <git@davidb.org>
Date: Dec 8, 2007, 03:37 UTC
Message-ID: <20071208033722.GA27776@old.davidb.org>
In-Reply-To: <9e4733910712071929h17a7d88dv37686ec7cd858c63@mail.gmail.com>

On Fri, Dec 07, 2007 at 10:29:31PM -0500, Jon Smirl wrote:

Show 9 quoted lines

>The kernel repo has the same problem but not nearly as bad.
>
>Starting from a default pack
> git repack -a -d -f  --depth=1000 --window=1000
>Uses 1GB of physical memory
>
>Now do the command again.
> git repack -a -d -f  --depth=1000 --window=1000
>Uses 1.3GB of physical memory

With my repo that contains a bunch of 50MB tarfiles, I've found I must specify --window-memory as well to keep repack from using nearly unbounded amounts of memory. Perhaps it is the larger files found in gcc that provokes this.

A window size of 1000 can take a lot of memory if the objects are large.

Dave