From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jan Holesovsky <kendy@suse.cz>
Cc: Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org, releases@openoffice.org
Subject: Re: Git benchmarks at OpenOffice.org wiki
Date: Wed, 2 May 2007 16:35:17 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705021630170.4015@racer.site> (raw)
In-Reply-To: <200705021624.25560.kendy@suse.cz>
Hi,
On Wed, 2 May 2007, Jan Holesovsky wrote:
> On Tuesday 01 May 2007 23:46, Jakub Narebski wrote:
>
> > What I am concerned about is some of git benchmark results at Git page
> > on OpenOffice.org wiki:
> > http://wiki.services.openoffice.org/wiki/Git#Comparison
> > Actually it is comparison with CVS and Subversion, although most
> > benchmarks are done only for git.
>
> I did the git numbers, so if they are wrong - blame me :-)
Good to have you here!
> > 'Checkout time' (which should be renamed to 'Initial checkout time'),
> > in which git also loses with 130 minutes (Linux, 2MBit DSL) [from
> > go-oo.org], 100min (Linux, 2MBit DSL, Wireless, no proxy) [from
> > go-oo.org] versus 117 minutes (Linux, 2MBit DSL), 26 minutes (Linux,
> > 2MBit DSL, with compression (-z 6)) for CVS, and 60 Minutes (Windows,
> > 34Mbit Line) for Subversion, would also be helped by the above.
>
> Good point, and I already changed the page in the morning. I also added the
> checkout time that I got over a fast line [it was 44min].
It took me longer here, but the reason might be that my "local" repository
is on NFS, due to quota on the machine.
> > What I'm really concerned about is branch switch and merging branches,
> > when one of the branches is an old one (e.g. unxsplash branch), which
> > takes 3min (!) according to the benchmark. 13-25sec for commit is also
> > bit long, but BRANCH SWITCHING which takes 3 MINUTES!? There is no
> > comparison benchmark for CVS or Subversion, though...
I imagine that might be related to the vast amount of remote branches.
IIRC we do not pack them with git-gc, and ext3 is not that good with big
directories (remember: 3464 branches!).
Maybe oprofile knows a bit more where the hotspots are.
Ciao,
Dscho
next prev parent reply other threads:[~2007-05-02 14:35 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
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 [this message]
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=Pine.LNX.4.64.0705021630170.4015@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=kendy@suse.cz \
--cc=releases@openoffice.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).