git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] hash binary sha1 into patch id

From
Marat Radchenko <marat@slonopotamus.org>
Date
Oct 14, 2010, 07:19 UTC
Message-ID
<1287040761027-5633988.post@n2.nabble.com>
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.
Previous: Clemens Buchacher
Message 13 of 13 in “hash binary sha1 into patch id”
  1. hash binary sha1 into patch idClemens Buchacher, Aug 13, 2010
  2. Jonathan NiederAug 13, 2010
  3. Clemens BuchacherAug 13, 2010
  4. Jonathan NiederAug 13, 2010
  5. Clemens BuchacherAug 13, 2010
  6. hash binary sha1 into patch idClemens Buchacher, Aug 15, 2010
  7. Jonathan NiederAug 15, 2010
  8. Marat RadchenkoSep 10, 2010
  9. Clemens BuchacherSep 10, 2010
  10. Marat RadchenkoOct 13, 2010
  11. Marat RadchenkoOct 13, 2010
  12. Clemens BuchacherOct 13, 2010
  13. Marat RadchenkoOct 14, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.