git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: q: git-fetch a tad slow?
Date: Thu, 31 Jul 2008 23:03:07 +0200	[thread overview]
Message-ID: <20080731210307.GF25138@elte.hu> (raw)
In-Reply-To: <20080731044531.GB1860@spearce.org>


* Shawn O. Pearce <spearce@spearce.org> wrote:

> Ingo Molnar <mingo@elte.hu> wrote:
> > 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?

the client side on titan has:

 titan:~> git version
 git version 1.5.2.2

oldish but not outrageously old, right?

 server side has:

 earth4:~> git version
 git version 1.5.6.1.108.g660379

> 
> 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.

ah, it is a shell script indeed! I'll upgrade to latest.

	Ingo

  reply	other threads:[~2008-07-31 21:04 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
2008-07-31  4:45         ` Shawn O. Pearce
2008-07-31 21:03           ` Ingo Molnar [this message]
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=20080731210307.GF25138@elte.hu \
    --to=mingo@elte.hu \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).