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

Re: gitk performance questions/issues

From
Paul Mackerras <paulus@samba.org>
Date
Aug 14, 2007, 04:39 UTC
Message-ID
<18113.12777.164103.302185@cargo.ozlabs.ibm.com>
In-Reply-To
<e1dab3980708131018h495c5cf2m76cb8f6ffc4df6dc@mail.gmail.com>
David Tweed writes:
> Thinking about it, I suppose even if you're only looking at the last
> 256 commits you've got to look through all the tags to see whether
> or not they refer to something within that window, so it's not
> unreasonable for it to affect startup time.

Gitk uses a Tcl associative array for that, which should be very fast.

Could you try this: go to the Edit->Preferences window and turn off "Display nearby tags". Then with your ~2000 refs in place, see how long gitk takes to start up and to display a diff.

If doing that makes it fast, then I suspect that my topology caching patch will also help. That's waiting on an answer from Junio or Linus to my question about making git rev-list ignore negated non-existent refs.

Also, if it's possible to give me a copy of your repo, that would help.

Paul.
Previous: David TweedNext: David Tweed
Message 4 of 5 in “gitk performance questions/issues”
  1. David TweedAug 13, 2007
  2. Linus TorvaldsAug 13, 2007
  3. David TweedAug 13, 2007
  4. Paul MackerrasAug 14, 2007
  5. David TweedAug 14, 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.