Re: Progress report on git-blame

[David Kastrup]

Óscar Fuentes <address@hidden> writes:

> Some random data points:
>
> $ time git blame -L 1000,+100 -- src/xdisp.c > /dev/null
>
> real    0m11.034s
> user    0m10.417s
> sys     0m0.599s
>
>
> $ time git blame -L 1000,+1000 -- src/xdisp.c > /dev/null
>
> real    0m15.089s
> user    0m14.297s
> sys     0m0.767s
>
>
> $ time git blame -L 1000,+10000 -- src/xdisp.c > /dev/null
>
> real    1m5.144s
> user    1m3.555s
> sys     0m1.502s
>
>
> It seems that there is not a lot of a difference among blaming 20 lines
> and blaming 1000.

It very much depends on _which_ lines.  Basically, lines forming a block
sticking together when doing a unified diff are not all that expensive
since they travel in a single data structure.  The worst are lots of
small changes introduced in different branches.

> AFAIK current `blame' functionality on VC (and on git-blame.el) is
> based on working on the whole file,

Sure?  If so, it maybe should at least be made to support git blame
--incremental usefully.

-- 
David Kastrup