Re: Git is not scalable with too many refs/*
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 26, 2011, 20:07 UTC
- Message-ID
- <7vvcsf130i.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <201109261401.38624.mfick@codeaurora.org>
Martin Fick <mfick@codeaurora.org> writes:
Show 6 quoted lines
> After a gc, the repo does perform the similar to the > uncompressed one (which was achieved via gc). After gc, it > takes ~.05s do to a 'git branch' with 1.7.6 and > git.1.7.7.rc0.72.g4b5ea. It also takes a bit more than 15s > with the patch reverted. So it appears that compression is > not likely the culprit, but rather the need to be gced.
Isn't packing refs part of "gc" these days?