From: Junio C Hamano <gitster@pobox.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "Avery Pennarun" <apenwarr@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: update-index --assume-unchanged doesn't make things go fast
Date: Wed, 25 Jun 2008 12:41:11 -0700 [thread overview]
Message-ID: <7v1w2l1ew8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <m33an1josg.fsf@localhost.localdomain> (Jakub Narebski's message of "Wed, 25 Jun 2008 12:30:21 -0700 (PDT)")
Jakub Narebski <jnareb@gmail.com> writes:
> "Avery Pennarun" <apenwarr@gmail.com> writes:
>
>> Hi all,
>>
>> Using git 1.5.6.64.g85fe, but this applies to various other versions
>> I've tried.
>>
>> I have a git repo with about 17000+ files in 1000+ directories. In
>> Linux, "git status" runs in under a second, which is perfectly fine.
>> But on Windows, which can apparently only stat() about 1000 files per
>> second, "git status" takes at least 17 seconds to run, even with a hot
>> cache. (I've confirmed that stat() is so slow on Windows by writing a
>> simple program that just runs stat() in a tight loop. The slowness
>> may be cygwin-related, as I found some direct Win32 calls that seem to
>> go more than twice as fast... which is still too slow.)
>
> Which git version do you use? Does it have the following configuration
> variable (also available as command option):
>
> status.showUntrackedFiles::
> By default, linkgit:git-status[1] and linkgit:git-commit[1] show
> files which are not currently tracked by Git. Directories which
> contain only untracked files, are shown with the directory name
> only. Showing untracked files means that Git needs to lstat() all
> all the files in the whole repository, which might be slow on some
> systems. So, this variable controls how the commands displays
> the untracked files. Possible values are:
>
> - 'no' - Show no untracked files
> - 'normal' - Shows untracked files and directories
> - 'all' - Shows also individual files in untracked directories.
That's on 'master' progressing forward to eventually become 1.6.0.
next prev parent reply other threads:[~2008-06-25 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 16:44 update-index --assume-unchanged doesn't make things go fast Avery Pennarun
2008-06-25 17:38 ` Michael J Gruber
2008-06-25 18:02 ` Avery Pennarun
2008-06-26 8:47 ` Michael J Gruber
2008-06-25 19:30 ` Jakub Narebski
2008-06-25 19:41 ` Junio C Hamano [this message]
2008-06-25 19:53 ` Avery Pennarun
2008-06-25 21:35 ` Jakub Narebski
2008-06-26 1:30 ` Avery Pennarun
2008-06-26 11:22 ` Stephen R. van den Berg
2008-06-27 17:01 ` Avery Pennarun
2008-06-27 17:31 ` Jakub Narebski
2008-06-27 17:56 ` Avery Pennarun
2008-06-27 18:09 ` Dana How
2008-06-27 18:51 ` Avery Pennarun
2008-06-28 2:03 ` 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=7v1w2l1ew8.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).