From: Jeff King <peff@peff.net>
To: Joey Hess <joey@kitenet.net>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: speed of git reset -- file
Date: Wed, 1 Jun 2011 23:18:31 -0400 [thread overview]
Message-ID: <20110602031831.GA21008@sigill.intra.peff.net> (raw)
In-Reply-To: <20110601233157.GA2468@gnu.kitenet.net>
On Wed, Jun 01, 2011 at 07:31:57PM -0400, Joey Hess wrote:
> Cold cache:
> [...]
> 28.846625099 seconds time elapsed
>
> Warm cache is 0.88 seconds, but cold cache is typical; I use a cheap netbook
> for a lot of different stuff.
Yeah, it is going to be painful on a cold cache. But I wonder whether
your workflow would really permit the "reset" thing to make a
difference. That is, are you doing "git reset -- file" from a cold
cache, and then doing _nothing_ else with git? Because while yes, it may
be annoying for the "reset" to take 30 seconds, it's warming the cache
so that the subsequent "diff" or "status" will take 29.1 seconds less.
Which isn't to say I'm not sympathetic to the performance problems of
large repos on a cold cache. But I'm not sure there's really a way
around that. You're going to want to see the stat information eventually
if you are doing anything meaningful with git, and once it's loaded, the
warm cache delay isn't too bad. Trying to avoid it seems like a losing
battle.
-Peff
next prev parent reply other threads:[~2011-06-02 3:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 19:00 speed of git reset -- file Joey Hess
2011-05-31 21:26 ` Jeff King
2011-05-31 21:54 ` Junio C Hamano
2011-05-31 22:13 ` Jeff King
2011-05-31 22:13 ` Matthieu Moy
2011-06-01 1:14 ` Nguyen Thai Ngoc Duy
2011-05-31 23:39 ` Junio C Hamano
2011-06-01 19:58 ` Jeff King
2011-06-01 20:16 ` Joey Hess
2011-06-01 21:18 ` Jeff King
2011-06-01 22:05 ` Joey Hess
2011-06-01 22:56 ` Jeff King
2011-06-01 23:31 ` Joey Hess
2011-06-02 3:18 ` Jeff King [this message]
2011-06-02 4:36 ` Joey Hess
2011-06-02 4:46 ` Joey Hess
2011-06-01 20:51 ` Junio C Hamano
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=20110602031831.GA21008@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=joey@kitenet.net \
/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).