Re: git annotate runs out of memory

From: Marco Costalba <mcostalba@gmail.com>
Date: Dec 11, 2007, 19:14 UTC
Message-ID: <e5bfff550712111114s4e9c31cxb7aed4da70d23382@mail.gmail.com>
In-Reply-To: <4aca3dc20712111103s1af3b045h484ea749378c6282@mail.gmail.com>

On Dec 11, 2007 8:03 PM, Daniel Berlin <dberlin@dberlin.org> wrote:

Show 12 quoted lines

>
> > I don't know *how* file history is stored in the others scm, perhaps
> > is easier to retrieve, i.e. without a full walk across the
> > revisions...
>
> It is stored in an easier format. However, can you not simply provide
> side-indexes to do the annotation?
>
> I guess that own't work in git because you can change history (in
> other scm's, history is readonly so you could know the results for
> committed revisions will never change).
>

As Linus pointed out annotation in git is "much slower and much more costly than just having a local history view to begin with".

Indeed to annotate say kernel/sched.c

the time is spent by git while executing

git log -p -- kernel/sched.c

could be also 10X higher the the following annotation processing time starting from the git log output.

Unfortunately my knowledge of git internals falls far far shorter then guessing what could be done to increase the *one file* history case that _seems_ to be the common one.

Show 5 quoted lines

> > I would be interested in cold start and warm cache start (close the
> > annotation tab and start annotation again).
>
> I will try to do this.
>

Thanks. Very appreciated.