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

Re: git fetch slow as molasses due to tag downloading

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 14, 2006, 16:05 UTC
Message-ID
<Pine.LNX.4.63.0612141701440.3635@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<elrr8j$a02$1@sea.gmane.org>
Hi,
On Thu, 14 Dec 2006, Han-Wen Nienhuys wrote:
Show 11 quoted lines
> just upgraded our autobuilder from 1.4.3 to 1.4.4.2.
> 
> Now, our standard download command comes to a complete halt.  Judging
> >from the "ps -ef" apparently, it does 
> 
>    git-show-ref --verify --quiet -- [TAG]
> 
> This is done for every one of the 1500 tags that are in my repository. 
> At approx 20 tags per second this takes an awful lot of time. 
> 
> 1. Is this necessary? 
Yes. The purpose is to check which tags have not yet been fetched.
> 2. Is this efficient?  Wouldn't doing all tags in a single git-show-ref 
> invocation be potentially quicker?

It is not efficient. But it cannot be solved like you propose, since it is inside a loop, and a "continue" is executed when the tag exists already.

IMHO this should be solved as a filter: "git-show-ref --stdin --show-invalid". Thus, git does not have to traverse _every_ ref for _every_ incoming tag.

Ciao, Dscho

Previous: Han-Wen NienhuysNext: Jakub Narebski
Message 2 of 5 in “git fetch slow as molasses due to tag downloading”
  1. Han-Wen NienhuysDec 14, 2006
  2. Johannes SchindelinDec 14, 2006
  3. Jakub NarebskiDec 15, 2006
  4. Junio C HamanoDec 15, 2006
  5. Jakub NarebskiDec 15, 2006

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.