From: bdowning@lavos.net (Brian Downing)
To: Junio C Hamano <junio@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2008, #04; Sun, 17)
Date: Mon, 18 Aug 2008 17:41:05 -0500 [thread overview]
Message-ID: <20080818224105.GA31114@lavos.net> (raw)
In-Reply-To: <7vej4o6j40.fsf@gitster.siamese.dyndns.org>
On Sun, Aug 17, 2008 at 03:17:35AM -0700, Junio C Hamano wrote:
> * bd/diff-strbuf (Wed Aug 13 23:18:22 2008 -0700) 3 commits
> + xdiff-interface: hide the whole "xdiff_emit_state" business from
> the caller
> + Use strbuf for struct xdiff_emit_state's remainder
> + Make xdi_diff_outf interface for running xdiff_outf diffs
>
> Gives measurable performance improvement to textual diff generation. For
> improving "blame" performance, it might be more effective to hook directly
> to lower level of xdiff machinery so that we do not even have to generate
> patch only to discard after reading "@@ -l,k +m,n @@" lines, but that
> would be a separate topic.
I have done this, resulting in my blame test case going from about 100s
on master to about 50s, but I need to do some additional cleanup before
it's ready to be submitted. I also have some more ideas for how to
speed it up some more. (Basically, with the textual diff generation
removed, most of the time now is spent in xdiff hashing lines. Since
blame in copy-detection mode tends to diff against the same file over
and over again, this is wasted work. Allowing the xdiff machinery to
re-use a diff preparation looks to be a little involved, though...)
-bcd
prev parent reply other threads:[~2008-08-18 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-17 10:17 What's cooking in git.git (Aug 2008, #04; Sun, 17) Junio C Hamano
2008-08-17 11:44 ` Tor Arvid Lund
2008-08-18 22:41 ` Brian Downing [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080818224105.GA31114@lavos.net \
--to=bdowning@lavos.net \
--cc=git@vger.kernel.org \
--cc=junio@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox