From: Sean <seanlkml@sympatico.ca>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
moe <moe-git@mbox.bz>,
git@vger.kernel.org
Subject: Re: git and larger trees, not so fast?
Date: Thu, 9 Aug 2007 16:52:18 -0400 [thread overview]
Message-ID: <20070809165218.9b76ebf7.seanlkml@sympatico.ca> (raw)
In-Reply-To: <7v7io4xwvp.fsf@assigned-by-dhcp.cox.net>
On Thu, 09 Aug 2007 13:42:50 -0700
Junio C Hamano <gitster@pobox.com> wrote:
> I do not know if this "fixes" the performance problem or not (I
> do not have that much time during the day), so I would not call
> this a "fix" yet, but at least the _change_ looks trivially
> correct, and passes all the existing tests.
>
> Interested parties may want to try it and see if it shifts the
> bottleneck.
Junio,
This makes things _much_ better, however the final commit in the
test script still shows a lot of user time:
## time git init
real 0m0.005s
user 0m0.001s
sys 0m0.004s
## time git add .
real 0m3.501s
user 0m1.268s
sys 0m2.159s
## time git commit -q -m 'buurrrrn' -a
real 0m2.299s
user 0m1.065s
sys 0m1.317s
## time git status
real 0m1.107s
user 0m0.548s
sys 0m0.557s
## time git status
real 0m1.122s
user 0m0.545s
sys 0m0.557s
## time git status
real 0m1.142s
user 0m0.545s
sys 0m0.576s
## time git commit -q -m 'hurry' 50/500
real 0m16.944s
user 0m15.466s
sys 0m1.133s
Cheers,
Sean
next prev parent reply other threads:[~2007-08-09 20:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 16:30 git and larger trees, not so fast? moe
2007-08-09 17:11 ` Linus Torvalds
2007-08-09 17:38 ` Linus Torvalds
2007-08-09 18:00 ` Junio C Hamano
2007-08-09 18:06 ` Linus Torvalds
2007-08-09 18:11 ` Junio C Hamano
2007-08-09 20:42 ` Junio C Hamano
2007-08-09 20:52 ` Sean [this message]
2007-08-09 21:37 ` Junio C Hamano
2007-08-09 21:41 ` Linus Torvalds
2007-08-09 21:46 ` Linus Torvalds
2007-08-09 22:02 ` Junio C Hamano
2007-08-09 23:38 ` Junio C Hamano
2007-08-10 0:04 ` Junio C Hamano
2007-08-10 0:44 ` Linus Torvalds
2007-08-10 0:51 ` Junio C Hamano
2007-08-10 0:57 ` Linus Torvalds
2007-08-10 3:48 ` Junio C Hamano
2007-08-10 5:55 ` Junio C Hamano
2007-08-10 15:49 ` Linus Torvalds
2007-08-10 16:07 ` Linus Torvalds
2007-08-10 16:51 ` Fix "git commit directory/" performance anomaly Linus Torvalds
2007-08-10 17:14 ` Linus Torvalds
2007-08-10 18:31 ` Junio C Hamano
2007-08-10 18:56 ` Linus Torvalds
2007-08-10 1:42 ` git and larger trees, not so fast? Daniel Barkalow
2007-08-09 17:54 ` Linus Torvalds
2007-08-09 18:06 ` David Kastrup
2007-08-10 19:39 ` Linus Torvalds
2007-08-11 18:47 ` Linus Torvalds
2007-08-11 19:02 ` Fernando J. Pereda
2007-08-11 20:38 ` Linus Torvalds
2007-08-11 20:51 ` Fernando J. Pereda
2007-08-11 22:27 ` Linus Torvalds
2007-08-11 23:26 ` David Kastrup
2007-08-11 20:06 ` moe
2007-08-23 0:30 ` moe
-- strict thread matches above, loose matches on Subject: below --
2007-08-09 16:06 moe
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=20070809165218.9b76ebf7.seanlkml@sympatico.ca \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=moe-git@mbox.bz \
--cc=torvalds@linux-foundation.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).