From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff King <peff@peff.net>, John Keeping <john@keeping.me.uk>,
Jim Kinsman <jakinsman@gmail.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git status takes 30 seconds on Windows 7. Why?
Date: Wed, 27 Mar 2013 13:00:26 -0700 [thread overview]
Message-ID: <7vy5d8lijp.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CA+55aFypcwbLwPLq++AU9FggCKLYkgkuN6i-gOD9pRioH1Dz2g@mail.gmail.com> (Linus Torvalds's message of "Wed, 27 Mar 2013 12:27:23 -0700")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Wed, Mar 27, 2013 at 12:04 PM, Jeff King <peff@peff.net> wrote:
>>
>> Yes, I think that's pretty much the case (though most of my
>> Git-on-Windows experience is from cygwin long ago, where the stat
>> performance was truly horrendous). Have you tried setting
>> core.preloadindex, which should run the stats in parallel?
>
> I wonder if preloadindex shouldn't be enabled by default.
I am surprised that we haven't done so.
Given that we haven't tweaked the parallelism or thread-cost
parameters since the inception of the mechanism in Nov 2008, I
suspect that we would see praises from some and grievances from
other corners of the user base for a while until we find acceptable
values for them, but I agree the feature has been in use
sufficiently by some people (heh, I just discovered that I don't
have it in my config), it can be the default.
next prev parent reply other threads:[~2013-03-27 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 16:39 git status takes 30 seconds on Windows 7. Why? Jim Kinsman
2013-03-27 16:44 ` Andreas Ericsson
2013-03-27 17:02 ` Konstantin Khomoutov
2013-03-27 17:17 ` Matthieu Moy
2013-03-27 18:15 ` Jim Kinsman
2013-03-27 18:46 ` John Keeping
2013-03-27 19:04 ` Jeff King
2013-03-27 19:27 ` Linus Torvalds
2013-03-27 20:00 ` Junio C Hamano [this message]
2013-03-27 20:12 ` Linus Torvalds
2013-03-27 17:22 ` John Keeping
2013-03-28 1:19 ` Duy Nguyen
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=7vy5d8lijp.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=jakinsman@gmail.com \
--cc=john@keeping.me.uk \
--cc=peff@peff.net \
--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).