Re: gc getting called on each git command ... what's wrong?

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 8, 2011, 16:50 UTC
Message-ID: <7vhb802row.fsf@alter.siamese.dyndns.org>
In-Reply-To: <1307548930.19438.30.camel@drew-northup.unet.maine.edu>

Drew Northup <drew.northup@maine.edu> writes:

Show 7 quoted lines

>> That's why. See gc.autopacklimit in "git help config" -- by default,
>> git will gc if there are more than 50 pack files.
>
> Do we want to consider ignoring (or automatically doubling, or something
> like that) gc.autopacklimit if that number of packs meet or exceed
> gc.packSizeLimit? I have no idea what the patch for this might look
> like, but it seems to make more sense than this situation.

This is unrelated to the auto-gc, but it also would be fruitful to question if it is a sane setting to limit packfiles to 30M, when the repository needs 100 of them (total around 3G??). Just like having too many loose object files degrade performance (and that is one of the reasons we pack them in the first place), having many packs will degrade performance unnecessarily and to a worse degree, as "check which pack has this particular object" code has to examine all packs, unlike the loose object case where we let the .git/objects/?? fan-out to give us some hashing and the filesystem to do the heavylifting for us.