From: "Shawn O. Pearce" <spearce@spearce.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: git@vger.kernel.org
Subject: Re: q: git-fetch a tad slow?
Date: Wed, 30 Jul 2008 15:38:14 -0700 [thread overview]
Message-ID: <20080730223814.GF28503@spearce.org> (raw)
In-Reply-To: <20080730190657.GC26389@elte.hu>
Ingo Molnar <mingo@elte.hu> wrote:
> * 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).
> > 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.
next prev parent reply other threads:[~2008-07-30 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 16:01 q: git-fetch a tad slow? Ingo Molnar
2008-07-29 5:50 ` Shawn O. Pearce
2008-07-29 9:08 ` Ingo Molnar
2008-07-30 4:48 ` Shawn O. Pearce
2008-07-30 19:06 ` Ingo Molnar
2008-07-30 22:38 ` Shawn O. Pearce [this message]
2008-07-31 4:45 ` Shawn O. Pearce
2008-07-31 21:03 ` Ingo Molnar
2008-07-31 21:11 ` Ingo Molnar
2008-07-31 21:19 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080730223814.GF28503@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.