From: Linus Torvalds <torvalds@linux-foundation.org>
To: moe <moe-git@mbox.bz>
Cc: git@vger.kernel.org
Subject: Re: git and larger trees, not so fast?
Date: Sat, 11 Aug 2007 11:47:42 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0708111137250.30176@woody.linux-foundation.org> (raw)
In-Reply-To: <20070809163026.GD568@mbox.bz>
On Thu, 9 Aug 2007, moe wrote:
>
> here's a test-case (should be safe to
> copy/paste on linux, bash):
moe: with current git (and thus the 1.5.3 release), the "git status"
commands now take half a second for me, and the git commit takes just
under a second.
The *initial* commit that adds everything still takes almost 5 seconds,
but that was due to generating the diffstat summary - with a "-q" on the
commit line that too drops down to just under a second.
In fact, the only thing that took more than a second for me with the
current git is that initial "git add .", which took 1.791s for me.
Considering that it had to hash all the 100,000 objects, I'm not
surprised.
Anyway, it would be good if you re-did your real work tree with current
commit, just to verify. You have slower hardware than I do, but hopefully
it is now just about as fast as it can be.
Linus
next prev parent reply other threads:[~2007-08-11 18:48 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
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 [this message]
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=alpine.LFD.0.999.0708111137250.30176@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=moe-git@mbox.bz \
/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).