From: Matt Mackall <mpm@selenic.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
git@vger.kernel.org, mercurial@selenic.com,
Linus Torvalds <torvalds@osdl.org>
Subject: Mercurial 0.4e vs git network pull
Date: Thu, 12 May 2005 02:44:06 -0700 [thread overview]
Message-ID: <20050512094406.GZ5914@waste.org> (raw)
Now that I'm back from vacation, there's a new Mercurial release as
well as snapshots at:
http://selenic.com/mercurial/
A combined self-hosting repository / web interface can be found at:
http://selenic.com/hg/
And there's now a mailing list at:
http://selenic.com/mailman/listinfo/mercurial
The big news is that Mercurial now has a very fast network protocol.
This benchmark is pulling and merging 819 changesets (again, taken
from 2.6.12-rc2-mm3) from one repo to another over DSL using
Mercurial's new delta protocol:
$ time hg merge hg://selenic.com/linux-hg/
retrieving changegroup
merging changesets
merging manifests
merging files
real 0m10.276s
user 0m3.299s
sys 0m0.689s
For comparison, rsyncing the same set of changes between git repos from
the same server:
$ time rsync -a rsync://10.0.0.12:2000/git/lgb/.git .
sent 171508 bytes received 31225542 bytes 312408.46 bytes/sec
real 1m40.470s
user 0m0.655s
sys 0m1.896s
The original broken-out.tar.bz2: 2.3M
The same, uncompressed: 15M
The same, rsynced with git: 30M
The same, pulled with hg (zlib): 2.5M <- what I used above
The same, pulled with hg (bz2): 2.1M
The server in question is a relatively busy 1GHz Athlon. The server
side of the hg protocol is stateless and is serviced by a simple CGI
script run under Apache.
Mercurial is more than 10 times as bandwidth efficient and
considerably more I/O efficient. On the server side, rsync uses about
twice as much CPU time as the Mercurial server and has about 10 times
the I/O and pagecache footprint as well.
Mercurial is also much smarter than rsync at determining what
outstanding changesets exist. Here's an empty pull as a demonstration:
$ time hg merge hg://selenic.com/linux-hg/
retrieving changegroup
real 0m0.363s
user 0m0.083s
sys 0m0.007s
That's a single http request and a one line response.
And now with rsync:
$ time rsync -av rsync://10.0.0.12:2000/git/lgb/.git .
receiving file list ... done
sent 76 bytes received 1280245 bytes 2560642.00 bytes/sec
total size is 85993841 speedup is 67.17
real 0m0.539s
user 0m0.185s
sys 0m0.148s
Mercurial's communication here scales O(min(changed branches, log new
changesets)) which is less than O(new changesets), while rsync scales
with O(total number of file revisions) (ouch!). The above transfer
size for an empty pull will go from 1.2M to >12M when there's similar
history in git to what's in BK.
--
Mathematics is the supreme nostalgia of our time.
next reply other threads:[~2005-05-12 9:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 9:44 Matt Mackall [this message]
2005-05-12 18:23 ` Mercurial 0.4e vs git network pull Petr Baudis
2005-05-12 20:11 ` Matt Mackall
2005-05-12 20:14 ` Petr Baudis
2005-05-12 20:57 ` Matt Mackall
2005-05-12 21:24 ` Daniel Barkalow
2005-05-12 22:29 ` Matt Mackall
2005-05-13 0:33 ` Daniel Barkalow
2005-05-13 1:11 ` Matt Mackall
2005-05-13 2:23 ` Daniel Barkalow
2005-05-13 2:44 ` Matt Mackall
2005-05-13 5:44 ` Petr Baudis
2005-05-15 8:54 ` Petr Baudis
2005-05-15 6:22 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2005-05-15 11:22 Adam J. Richter
2005-05-15 12:40 ` Petr Baudis
2005-05-16 22:22 ` Tristan Wibberley
2005-05-15 17:39 ` Matt Mackall
2005-05-15 18:23 ` Jeff Garzik
2005-05-16 1:12 ` Matt Mackall
2005-05-16 9:29 ` Matthias Urlichs
2005-05-15 11:52 Adam J. Richter
2005-05-15 14:23 ` Petr Baudis
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050512094406.GZ5914@waste.org \
--to=mpm@selenic.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mercurial@selenic.com \
--cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).