Re: gc --aggressive
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 17, 2012, 22:17 UTC
- Message-ID
- <7vr4vmm29z.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <20120417220838.GB10797@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 9 quoted lines
> ... > I wonder where the memory is going. In theory, the memory consumption > for packing comes from keeping all of the objects for a given window in > memory (so we are looking for a delta for object X, and we have a window > of Y[0]..Y[$window] objects that we will consider). And for a > multi-threaded pack, that's per-thread. > > How many cores are there on this box? Have you tried setting > pack.windowMemory to (12 / # of cores) or thereabouts?
Hrm, from the end-user's point of view, it appears that pack.windowMemory ought to mean the total without having to worry about the division of it across threads (which the implementation should be responsible for).
> ... But it seems lame that git _can't_ > do a full repack on such a beefy machine. You don't want to do it all > the time, but you might want to do it at least once.
True.