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

Re: q: git-fetch a tad slow?

From
IMIngo Molnar <mingo@elte.hu>
Date
Jul 29, 2008, 09:08 UTC
Message-ID
<20080729090802.GA11373@elte.hu>
In-Reply-To
<20080729055014.GE11947@spearce.org>
* Shawn O. Pearce <spearce@spearce.org> wrote:
Show 8 quoted lines
> Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > Setup/background: distributed kernel testing cluster, [...]
> > 
> > Problem: i noticed that git-fetch is a tad slow:
> > 
> >   titan:~/tip> time git-fetch
> >   real    0m2.372s
> Also, I wonder if you really need to fetch over SSH.  Doing a fetch 
> over git:// is much quicker, as there is no SSH session setup 
> overheads.
note that titan is a very beefy box, almost 3 GHz Core2Duo:
   model name      : Intel(R) Core(TM)2 CPU         E6800  @ 2.93GHz
   stepping        : 5
   cpu MHz         : 2933.331

server is 3 GHz. So if we have a quadratic overhead on number of branches, that's going to be quite a PITA.

> I wonder if git-pack-refs + fetching only a single branch will get you 
> closer to the tip-fetch time.

should i pack on both repos? I dont explicitly pack anything, but on the server it goes into regular gc runs. (which will pack most stuff, right?)

	Ingo
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 3 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.