From: Christian Couder <christian.couder@gmail.com>
Date: Tue, 15 Nov 2016 11:44:42 GMT
Subject: Re: Git status takes too long- How to improve the performance of git
Message-ID: <CAP8UFD2tHW5_L4yPzVSxK2jpUKPKiq26sCnJ1Ts7R5TWiOpzEg@mail.gmail.com>
In-Reply-To: <20161115102400.GC28860@paksenarrion.iveqy.com>

On Tue, Nov 15, 2016 at 11:24 AM, Fredrik Gustafsson <iveqy@iveqy.com> wrote:
> On Tue, Nov 15, 2016 at 02:33:12AM -0700, ravalika wrote:

[...]

>> And I have experimented the following ways
>> -          -  Setting core.ignorestat to true
>> -          -  Git gc &git clean
>> -          -  Shallow clone – Reducing number of commits
>> -          -  Clone only one branch
>>       - Git repacking - git repack -ad && git prune
>> -     - Cold/warm cache
>>
>> Could you please let me know, what are the ways to improve the git
>> performance ?
>> I have gone through the mailing lists.
>
> You could always check the --assume-unchanged bit, see the manual page
> for git update-index. However this is quite extreme and demanding for
> the user.

If you install a recent version version, you may be able to use the
untracked cache feature.
(See "core.untrackedCache" in the git config documentation and
--untracked-cache in the git update-index documentation.)