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

Re: q: git-fetch a tad slow?

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jul 31, 2008, 04:45 UTC
Message-ID
<20080731044531.GB1860@spearce.org>
In-Reply-To
<20080730190657.GC26389@elte.hu>
Ingo Molnar <mingo@elte.hu> wrote:
Show 7 quoted lines
> alas, fetching still seems to be slow:
> 
>   titan:~/tip> time git-fetch origin
> 
>   real    0m5.112s
>   user    0m0.972s
>   sys     0m3.380s
What version of git are dealing with on the client side?

I only have a MacBook Pro (2.4 GHz Intel Core 2 Duo) and I'm getting fetch times of ~472 ms over git:// to your -tip.git tree and ~128 ms for strictly local fetch. If your SSH overhead is ~300 ms this is only a ~700 ms real time for `git fetch origin`, not 5100 ms.

Is your git-fetch a shell script? Or a compiled binary? The port into C made it go _much_ faster, even though it is still a naive O(N^2) matching algorithm. Yea, we still should fix that, but I think an upgrade to 1.5.4 or later would make the client side improve consideribly.

-- 
Shawn.
Previous: Shawn O. PearceNext: Ingo Molnar
Message 7 of 10 in “q: git-fetch a tad slow?”
  1. Ingo MolnarJul 28, 2008
  2. Shawn O. PearceJul 29, 2008
  3. Ingo MolnarJul 29, 2008
  4. Shawn O. PearceJul 30, 2008
  5. Ingo MolnarJul 30, 2008
  6. Shawn O. PearceJul 30, 2008
  7. Shawn O. PearceJul 31, 2008
  8. Ingo MolnarJul 31, 2008
  9. Ingo MolnarJul 31, 2008
  10. Shawn O. PearceJul 31, 2008

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.