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

git blame performance

From
JSJan Smets <jan.smets@alcatel-lucent.com>
Date
Nov 6, 2015, 13:37 UTC
Message-ID
<563CAD30.6040608@alcatel-lucent.com>
Hi

I have recently migrated a fairly large project from CVS to Git. One of the issues we're having is the blame/annotate performance.

The repository contains +650k commits total, of which ~300k are on master. (raw size = ~8GB)

Running blame on one of the oldest files takes over 30 seconds. This is on a fairly beefy (server) machine with lots of ram and the repository on a ramdisk. Running git 2.5.2

cvs annotate of the same file (over the network) is ready in 0.8 seconds. blame/annotate is a frequently used operation, ranging between 5 to 20 usages a day per developer.

I have two questions
  1) Is there a way to speed this up (in git)? eg: can it run multi 
threaded? build pre-cached blame views?
  2) I was thinking to work around the issue and use gitweb 
blame_incremental and pre-populate the cache.

If you can think of any other (short term) solutions I would really like to hear them.

Thank you
- Jan
Next: Michael Haggerty
Message 1 of 3 in “git blame performance”
  1. Jan SmetsNov 6, 2015
  2. Michael HaggertyNov 6, 2015
  3. Junio C HamanoNov 6, 2015

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.