From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git benchmarks at OpenOffice.org wiki
Date: Fri, 04 May 2007 01:36:27 +0200 [thread overview]
Message-ID: <f1drdk$7uj$1@sea.gmane.org> (raw)
In-Reply-To: 200705031216.19817.robin.rosenberg.lists@dewire.com
Robin Rosenberg wrote:
> torsdag 03 maj 2007 skrev Johannes Schindelin:
>> 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,
That is nice to know where the culprit is: 197000 files and 24000
directories (132 projects), i.e. huge tree and not enogh memory.
This is yet another reason for splitting OOo repository into subprojects.
I do wonder if git can be more conservative in memory usage...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-05-03 23:32 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
2007-05-03 10:48 ` Martin Langhoff
2007-05-06 20:05 ` Robin Rosenberg
2007-05-03 23:36 ` Jakub Narebski [this message]
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='f1drdk$7uj$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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.
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).