From: Andy Parkins <andyparkins@gmail•com>
To: git@vger•kernel.org
Cc: Jakub Narebski <jnareb@gmail•com>,
releases@openoffice•org, Jan Holesovsky <kendy@suse•cz>
Subject: Re: Git benchmarks at OpenOffice.org wiki
Date: Wed, 2 May 2007 09:55:02 +0100 [thread overview]
Message-ID: <200705020955.04582.andyparkins@gmail.com> (raw)
In-Reply-To: <200705012346.14997.jnareb@gmail.com>
On Tuesday 2007 May 01, Jakub Narebski wrote:
> In 'Size of data on the server' git has CVS beat hands down: 1.3G vs
> 8.5G for sources, 591M vs 1.1G for third party. I think it is similar
> for Subversion. I hope that repository is fully packed: IIRC the Mozilla
> CVS repository import was about 0.6GB pack file, not 1.3GB.
I'm fairly sure it's not. If so that would also affect the speed of
operations wouldn't it?
I also doubt the subversion checkout size - subversion keeps a pristine copy
of the HEAD file - so a subversion checkout is usually over twice the size of
the source tree.
> takes 3min (!) according to the benchmark. 13-25sec for commit is also
> bit long
I wonder if they are measuring the time for the generation of the commit
message or something? Or perhaps by using "git-commit -a" is causing a check
of the whole tree for changed files?
> Comparison / benchmark lacks some crucial info, like what computer was
> used (CPU, RAM, HDD), what filesystem was used, git version etc. It
> does have commands used for tests (benchmarks).
I'd also like to see some of the numbers for the other systems, I tried to use
subversion with the linux kernel once and got fed up waiting for it to do
anything. I suspect the reason numbers aren't shown for the others is that
they haven't finished yet :-)
> Could you confirm (or deny) those results? go-oo.org uses git 1.4.3.4;
> was there some improvement or bugfix related to the speed of checkout?
Wasn't there a recent change that made repacking after a clone unnecessary?
That would certainly reduce the checkout size.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail•com
next prev parent reply other threads:[~2007-05-02 8:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 21:46 Git benchmarks at OpenOffice.org wiki Jakub Narebski
2007-05-01 22:27 ` Junio C Hamano
2007-05-02 8:55 ` Andy Parkins [this message]
2007-05-02 9:51 ` Julian Phillips
2007-05-02 10:58 ` Andy Parkins
2007-05-02 14:28 ` Julian Phillips
2007-05-02 15:30 ` Andy Parkins
2007-05-02 17:11 ` Julian Phillips
2007-05-02 14:37 ` Jan Holesovsky
2007-05-02 15:33 ` Andy Parkins
2007-05-02 17:26 ` Junio C Hamano
2007-05-02 10:24 ` Johannes Schindelin
2007-05-02 11:33 ` Jakub Narebski
2007-05-02 14:55 ` Johannes Schindelin
2007-05-05 3:56 ` Linus Torvalds
2007-05-07 8:05 ` Junio C Hamano
2007-05-07 15:22 ` Linus Torvalds
2007-05-02 14:41 ` Jan Holesovsky
2007-05-02 16:24 ` Johannes Schindelin
2007-05-02 14:24 ` Jan Holesovsky
2007-05-02 14:35 ` Johannes Schindelin
2007-05-02 16:15 ` Petr Baudis
2007-05-02 16:27 ` Jan Holesovsky
2007-05-02 16:37 ` Petr Baudis
2007-05-02 16:48 ` Petr Baudis
2007-05-02 23:30 ` Jakub Narebski
2007-05-03 11:51 ` [tools-dev] " Jan Holesovsky
2007-05-03 12:54 ` Alex Riesen
2007-05-03 15:14 ` Johannes Sixt
2007-05-04 0:48 ` Jakub Narebski
2007-05-03 7:03 ` Florian Weimer
2007-05-03 9:33 ` Johannes Schindelin
2007-05-03 10:16 ` Robin Rosenberg
2007-05-03 10:48 ` Martin Langhoff
2007-05-06 20:05 ` Robin Rosenberg
2007-05-03 23:36 ` Jakub Narebski
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=200705020955.04582.andyparkins@gmail.com \
--to=andyparkins@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jnareb@gmail$(echo .)com \
--cc=kendy@suse$(echo .)cz \
--cc=releases@openoffice$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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