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 18:24:12 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705021822100.4015@racer.site> (raw)
In-Reply-To: <200705021641.53199.kendy@suse.cz>
Hi,
On Wed, 2 May 2007, Jan Holesovsky wrote:
> On Wednesday 02 May 2007 12:24, Johannes Schindelin wrote:
>
> > On Tue, 1 May 2007, Jakub Narebski wrote:
> > > '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.
> >
> > FWIW I can confirm the number "100min".
> >
> > Something I realized with pain is that the refs/ directory is 24MB big.
> > Yep. Really. They have 3464 heads and 2639 tags. I suspect that this is
> > the reason why.
>
> I should probably produce even a tree where would be the merged branches
> deleted, right...
FWIW, I just deleted all branches except for one, packed the tags, and did
a local clone (via NFS, urgh) _without_ checking the files out.
Now it takes 25 minutes vs 50 minutes before (in an _extremely_
unscientific test, mind you).
So, this issue is worth looking at, probably.
Ciao,
Dscho
next prev parent reply other threads:[~2007-05-02 16:24 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 [this message]
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
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=Pine.LNX.4.64.0705021822100.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.
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).