Re: q: git-fetch a tad slow?

From: Shawn O. Pearce <spearce@spearce.org>
Date: Jul 30, 2008, 22:38 UTC
Message-ID: <20080730223814.GF28503@spearce.org>
In-Reply-To: <20080730190657.GC26389@elte.hu>

Ingo Molnar <mingo@elte.hu> wrote:

Show 21 quoted lines

> * Shawn O. Pearce <spearce@spearce.org> wrote:
> > 
> > What does `find .git/refs -type f | wc -l` give for the repository on 
> > the central server?  If its more than a handful (~20) I would suggest 
> > running git-gc before testing again.
> 
> ah, you are right, it gave 275, then git-gc brought it down to two:
> 
>   earth4:~/tip> find .git/refs -type f | wc -l
>   275
>   earth4:~/tip> git gc
>   earth4:~/tip> find .git/refs -type f | wc -l
>   2
> 
> alas, fetching still seems to be slow:
> 
>   titan:~/tip> time git-fetch origin
> 
>   real    0m5.112s
>   user    0m0.972s
>   sys     0m3.380s

Yea, OK, there's definately performance problems there.  And it
should be fast.  Its too common of a case (fetching small deltas).

Show 11 quoted lines

> > I'll try to find some time to reproduce the issue and look at the 
> > bottleneck here.  I'm two days into a new job so my git time has been 
> > really quite short this week.  :-|
> 
> fetching the -tip repo:
> 
>    http://people.redhat.com/mingo/tip.git/README
> 
> and then running 'git remote update' will i think already show this 
> problem for you too. People have been complaining about how slow the 
> update is.

Thanks. I'll try to poke at it this evening and see what I find. git-fetch should be running faster than this.

-- 
Shawn.