From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Fernando J. Pereda" <ferdy@gentoo.org>
Cc: moe <moe-git@mbox.bz>, git@vger.kernel.org
Subject: Re: git and larger trees, not so fast?
Date: Sat, 11 Aug 2007 15:27:20 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0708111522570.30176@woody.linux-foundation.org> (raw)
In-Reply-To: <20070811205137.GC4710@ferdyx.org>
On Sat, 11 Aug 2007, Fernando J. Pereda wrote:
> >
> > What does "usable" mean? Is it still slow ("barely usable") or is it
> > actually fast enough to be truly _nice_ to use?
>
> Very nice to use considering my hardware is rather old. git status used
> to take >1m and it now takes ~3s and git commit takes ~7s while it used
> to take >1m too. So it makes things nice to use and I guess things are
> MUCH better on faster hardware.
Oh, ok. Having a 7s commit sounds fine - certainly not instantaneous, but
it doesn't sound too painful. Certainly not compared to what people live
with normally in some other environments, at least.
Thanks go to moe for just giving a trivial script to reproduce the
performance anomaly. It wasn't that hard to fix once there was a trivial
and unambiguous test case.
Linus
next prev parent reply other threads:[~2007-08-11 22:28 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
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 [this message]
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.0708111522570.30176@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=ferdy@gentoo.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).