git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Cc: David Kastrup <dak@gnu.org>
Subject: [PATCH 0/5] git-blame: further performance preview
Date: Mon,  3 Feb 2014 20:14:04 +0100	[thread overview]
Message-ID: <1391454849-26558-1-git-send-email-dak@gnu.org> (raw)

Ok, I'm progressing rather like molasses with getting -M and -C
options back to work.  In the mean time, here is another performance
preview without them.  The main patch in the middle has basically
gotten some formatting/style fixes as opposed to last time round and
one small bug fix (concerning incremental output).

It still contains a significant amount of dead code: this series is
not supposed to be merged, it's just supposed to be exciting to see
how it performs.

There are two simple performance patches on top of the main patch, the
first of which offers somewhat significant savings in I/O time (which
was quite unaffected by the main rewrite so far).  The gist of that
patch makes convenient use of the changed data layout to avoid
discarding blob data predictably required again right away.

It's likely that this is not the only opportunity to save performance
by better data management.

The second "performance" patch is not likely to measurably affect
overall performance.  Avoiding irrelevant iterations might make
debugging more pleasant, however.

David Kastrup (5):
  builtin/blame.c: struct blame_entry does not need a prev link
  Eliminate same_suspect function in builtin/blame.c
  builtin/blame.c: large-scale rewrite
  Performance improvement: don't drop origin blobs that are going to get
    tested next.
  Avoid queuing commits multiple times for the same origin

 builtin/blame.c | 595 +++++++++++++++++++++++++++++++++++---------------------
 1 file changed, 371 insertions(+), 224 deletions(-)

-- 
1.8.3.2

             reply	other threads:[~2014-02-03 19:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 19:14 David Kastrup [this message]
2014-02-03 19:14 ` [PATCH 1/5] builtin/blame.c: struct blame_entry does not need a prev link David Kastrup
2014-02-03 19:14 ` [PATCH 2/5] Eliminate same_suspect function in builtin/blame.c David Kastrup
2014-02-03 19:14 ` [PATCH 3/5] builtin/blame.c: large-scale rewrite David Kastrup
2014-02-03 19:14 ` [PATCH 4/5] Performance improvement: don't drop origin blobs that are going to get tested next David Kastrup
2014-02-03 19:14 ` [PATCH 5/5] Avoid queuing commits multiple times for the same origin David Kastrup

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=1391454849-26558-1-git-send-email-dak@gnu.org \
    --to=dak@gnu.org \
    --cc=git@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).