Re: git annotate runs out of memory

From: Daniel Berlin <dberlin@dberlin.org>
Date: Dec 11, 2007, 19:03 UTC
Message-ID: <4aca3dc20712111103s1af3b045h484ea749378c6282@mail.gmail.com>
In-Reply-To: <e5bfff550712111032p60fedbedu304cab834ce86eb9@mail.gmail.com>

On 12/11/07, Marco Costalba <mcostalba@gmail.com> wrote:

Show 11 quoted lines

> On Dec 11, 2007 6:33 PM, Daniel Berlin <dberlin@dberlin.org> wrote:
> >
> > Annotate is treasured by gcc developers (this was a key sticking point
> > in svn conversion).
> > Having an annotate that is 2x slower and takes 15x memory would not
> > fly (regardless of how good the results are).
> >
>
> Speed of annotation is mainly due to getting the file history more
> then calculating the actual annotation.
>

Yes, i figured as much.

> 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).

> 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.