Re: Performance issue of 'git branch'

From: Anders Kaseorg <andersk@mit.edu>
Date: Jul 23, 2009, 16:48 UTC
Message-ID: <alpine.DEB.1.10.0907231244020.10001@vinegar-pot.mit.edu>
In-Reply-To: <alpine.LFD.2.01.0907221921570.3352@localhost.localdomain>

On Wed, 22 Jul 2009, Linus Torvalds wrote:

> It uses the "raw" version of 'for_each_ref()' (which doesn't verify that 
> the ref is valid), and then does the "type verification" before it starts 
> doing any gentle commit lookup.

I submitted essentially the same patch in May:
  http://article.gmane.org/gmane.comp.version-control.git/120097
with the additional optimization that we don’t need to lookup commits at 
all unless we’re using -v, --merged, --no-merged, or --contains.  In my 
tests, it makes `git branch` 5 times faster on an uncached linux-2.6 
repository.

Anders

$ 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.