From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Florian Weimer <fw@deneb.enyo.de>, git@vger.kernel.org
Subject: Re: Git benchmarks at OpenOffice.org wiki
Date: Thu, 3 May 2007 12:16:05 +0200 [thread overview]
Message-ID: <200705031216.19817.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705031131410.4015@racer.site>
torsdag 03 maj 2007 skrev Johannes Schindelin:
> Hi,
>
> On Thu, 3 May 2007, Florian Weimer wrote:
>
> > * Jakub Narebski:
> >
> > > 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!?
> >
> > IIRC, GIT accesses every file in the tree, not just the ones that need
> > updating. How many files were actually updated when you changed
> > branches in your experiment?
>
> No. Git does not access every file, but rather all stats. That is a huge
> difference. And it should not take _that_ long for ~64000 files. Granted,
> it will cause a substantial delay, but not in the range of minutes.
It's worse... On my laptop the switch took ~ten minutes, not three.
A diff --stat takes over six minutes!! For reference, dd:in the pack
file with my disk takes ~50 seconds.
The reason is simple. I have a lousy one gigabyte RAM only, while
git wants 1.7GB virtual to do the diff-stat. and 800 MB resident. The swap is having a party,
$ vmstat 1
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
1 2 1861632 14108 428 126816 70 347 605 647 594 1041 11 2 74 13
0 2 1861204 12096 420 125724 3096 8 3096 24 625 1171 5 1 0 94
0 2 1860896 18972 404 115836 3524 292 3524 292 671 1474 7 4 0 89
0 2 1860820 18668 364 113736 3556 784 3556 784 669 1384 7 5 0 88
0 3 1860420 19692 300 109904 3008 180 3156 180 684 1325 8 5 0 87
0 3 1860184 18560 300 108596 3316 232 3396 232 643 1246 8 4 0 88
0 2 1859856 21808 292 103744 2108 32 2356 32 637 1319 9 1 0 90
-- robin
next prev parent reply other threads:[~2007-05-03 10:17 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
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 [this message]
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=200705031216.19817.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=fw@deneb.enyo.de \
--cc=git@vger.kernel.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).