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

git-log: --topo-order speed-ups the thing !?

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Jul 17, 2007, 19:13 UTC
Message-ID
<e5bfff550707171213m5969e436yf4db83c44a1c8c42@mail.gmail.com>

Testing with git log performance on Linux tree I found this interesting and unexpected result:

$ time git log --parents --boundary --pretty=raw -z --log-size --topo-order HEAD > /dev/null 6.85user 0.20system 0:07.05elapsed 100%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+21142minor)pagefaults 0swaps

$ time git log --parents --boundary --pretty=raw -z --log-size HEAD > /dev/null 7.01user 0.09system 0:07.10elapsed 100%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+11128minor)pagefaults 0swaps

Although page faults are more or less the half, execution time is faster _with_ --topo-order option.

Someone could explain why?

Thanks Marco

Message 1 of 1 in “git-log: --topo-order speed-ups the thing !?”
  1. Marco CostalbaJul 17, 2007

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.