git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Hengeveld <nickh@reactrix.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mike McCormack <mike@codeweavers.com>, git@vger.kernel.org
Subject: Re: Wine + GIT
Date: Tue, 6 Dec 2005 15:08:44 -0800	[thread overview]
Message-ID: <20051206230844.GA3876@reactrix.com> (raw)
In-Reply-To: <4394F50E.7030803@pobox.com>

On Mon, Dec 05, 2005 at 09:18:54PM -0500, Jeff Garzik wrote:

> One other comment:  http:// is the slowest of all three transports. 
> git:// (git daemon) is preferred, followed by rsync.
> 
> http:// takes forever, comparatively.

Has that been the general git user experience?  While there are
certainly disadvantages to the http transport, I didn't think that
performance was one of them.

For comparison, I ran some clones this morning/afternoon with the
following results:


Clone of kernel.org/pub/scm/git/git.git

http
real    0m24.204s       real    0m25.750s       real    0m24.094s
user    0m5.870s        user    0m5.530s        user    0m5.350s
sys     0m0.660s        sys     0m0.710s        sys     0m0.600s

rsync
real    1m3.952s        real    1m3.417s        real    1m4.360s
user    0m0.090s        user    0m0.130s        user    0m0.120s
sys     0m0.210s        sys     0m0.230s        sys     0m0.210s

git
real    0m54.715s       real    0m55.928s       real    0m56.411s
user    0m0.980s        user    0m0.980s        user    0m1.040s
sys     0m0.220s        sys     0m0.140s        sys     0m0.160s


Clone of kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

http
real    4m59.959s       real    5m28.512s       real    6m9.109s
user    1m38.400s       user    1m34.350s       user    1m35.700s
sys     0m7.640s        sys     0m8.180s        sys     0m7.510s

rsync
real    19m47.218s      real    19m46.739s      real    21m41.875s
user    0m3.960s        user    0m4.260s        user    0m4.000s
sys     0m5.060s        sys     0m4.680s        sys     0m4.860s

git
real    19m43.014s      real    19m36.692s      real    20m43.277s
user    0m23.180s       user    0m23.070s       user    0m23.230s
sys     0m8.210s        sys     0m8.590s        sys     0m11.240s

-- 
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.

  reply	other threads:[~2005-12-06 23:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05 23:29 Wine + GIT Mike McCormack
2005-12-06  2:03 ` Jeff Garzik
2005-12-06  2:26   ` Junio C Hamano
2005-12-06 17:08   ` J. Bruce Fields
2005-12-06 17:33     ` Junio C Hamano
2005-12-06 17:39       ` J. Bruce Fields
2005-12-06 17:53         ` Jon Loeliger
2005-12-06 21:22           ` git shorthands (was: Re: Wine + GIT) Andreas Ericsson
2005-12-07  0:56           ` Wine + GIT Ben Clifford
2005-12-06 19:01     ` Jeff Garzik
2005-12-06 19:06       ` Mike McCormack
2005-12-06  2:18 ` Jeff Garzik
2005-12-06 23:08   ` Nick Hengeveld [this message]
2005-12-06 23:27     ` Andreas Ericsson
2005-12-06  9:02 ` Marco Costalba
  -- strict thread matches above, loose matches on Subject: below --
2005-12-08  7:30 linux
2005-12-08  9:29 ` Fredrik Kuivinen
2005-12-08 18:17   ` Junio C Hamano

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=20051206230844.GA3876@reactrix.com \
    --to=nickh@reactrix.com \
    --cc=git@vger.kernel.org \
    --cc=jgarzik@pobox.com \
    --cc=mike@codeweavers.com \
    /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).