From: Marat Radchenko <marat@slonopotamus.org>
To: git@vger.kernel.org
Subject: Re: [PATCH v2] hash binary sha1 into patch id
Date: Thu, 14 Oct 2010 00:19:21 -0700 (PDT) [thread overview]
Message-ID: <1287040761027-5633988.post@n2.nabble.com> (raw)
In-Reply-To: <20101013211011.GA2558@localhost>
I'm running git-rev-list from git master in the form git rebase does:
git-rev-list --no-merges --cherry-pick --pretty=oneline --abbrev-commit
--abbrev=7 --reverse --left-right --topo-order FOO...BAR
New gprof output (I compiled without -O2 to prevent function inlining and
removed xecfg.flags = XDL_EMIT_FUNCNAMES):
http://git.661346.n2.nabble.com/file/n5633988/gprof_-p.txt gprof -p
http://git.661346.n2.nabble.com/file/n5633988/gprof_-q.txt gprof -q
This thing takes ~3 minutes of cpu time.
So, it takes ~3 minutes of cpu time and looks like all time is spent in
xdl_cleanup_records.
Repo info: 80GB, 200K revisions (~200 per working day), 500K files (15GB) in
master working copy, running git-rev-list to rebase ~5 commits over ~800
commits that happened upstream.
--
View this message in context: http://git.661346.n2.nabble.com/PATCH-hash-binary-sha1-into-patch-id-tp5419375p5633988.html
Sent from the git mailing list archive at Nabble.com.
prev parent reply other threads:[~2010-10-14 7:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 9:40 [PATCH] hash binary sha1 into patch id Clemens Buchacher
2010-08-13 20:00 ` Jonathan Nieder
2010-08-13 21:23 ` Clemens Buchacher
2010-08-13 21:37 ` Jonathan Nieder
2010-08-13 21:58 ` Clemens Buchacher
2010-08-15 7:20 ` [PATCH v2] " Clemens Buchacher
2010-08-15 7:56 ` Jonathan Nieder
2010-09-10 5:17 ` Marat Radchenko
2010-09-10 8:16 ` Clemens Buchacher
2010-10-13 7:46 ` Marat Radchenko
2010-10-13 9:17 ` Marat Radchenko
2010-10-13 21:10 ` Clemens Buchacher
2010-10-14 7:19 ` Marat Radchenko [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=1287040761027-5633988.post@n2.nabble.com \
--to=marat@slonopotamus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.