Re: git gc --aggressive led to about 40 times slower "git log --raw"

From: Duy Nguyen <pclouds@gmail.com>
Date: Feb 19, 2014, 10:24 UTC
Message-ID: <CACsJy8AQksxT-QROqxCKCjCzfqfz+SNN3=HTCjtRx3G-9GdnKg@mail.gmail.com>
In-Reply-To: <87bny3qxwr.fsf@fencepost.gnu.org>

On Wed, Feb 19, 2014 at 4:01 PM, David Kastrup <dak@gnu.org> wrote:

Show 9 quoted lines

> Calling git blame via C-x v g is a rather important part of the
> workflow, and it's currently intolerable to work with on a number of
> files.
>
> While I'm fixing the basic shortcomings in builtin/blame.c itself, the
> operation "fetch the objects" is necessary for all objects at least
> once.  It's conceivable that some nice caching strategy would help with
> avoiding the repeated traversal of long delta chain tails.  That could
> also help defusing the operation of basic stuff like git-log.

Pack v4 is supposed to tackle this delta chain thing, but its future is a bit uncertain (you can give a hand btw). If you often do "git blame", you might consider unpack most accessed objects (make it part of "blame" process), which would function exactly like a cache with no extra code. The downside is git-gc --auto is more likely to kick in because of too many loose objects and pack everything up again.

-- 
Duy