All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joey Hess <joey@kitenet.net>
To: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: speed of git reset -- file
Date: Wed, 1 Jun 2011 18:05:02 -0400	[thread overview]
Message-ID: <20110601220502.GA28493@gnu.kitenet.net> (raw)
In-Reply-To: <20110601211847.GA31958@sigill.intra.peff.net>

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

Jeff King wrote:
> > My experience with semi-large trees[1] is that I have to remember to use
> > "git status ." in a subdir; that "git commit -a" is of course slow when
> > I need to use it; and that the index gets big and things that need to
> > update it can become somewhat slow especially on slow disks, but that
> 
> Generally I find that the stats are very fast because everything is in
> cache, and the disk doesn't come into it at all. Are you on an OS
> besides Linux, or on a machine with low memory?

I have Linux and a gigabyte of ram and a not particularly good SSD.
Here `git reset file` takes 30 seconds, `git status` 45 seconds.

I do not seem to be alone in finding git reset file to be slow, the
problem was reported to me by another user.

> Yeah, Junio's autorefresh suggestion is much better.

That did seem reasonable and something I'd probably use.

-- 
see shy jo

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2011-06-01 22:05 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 [this message]
2011-06-01 22:56             ` Jeff King
2011-06-01 23:31               ` Joey Hess
2011-06-02  3:18                 ` Jeff King
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=20110601220502.GA28493@gnu.kitenet.net \
    --to=joey@kitenet.net \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.