Re: [PATCH/RFC] gitperformance: add new documentation about git performance tuning

[Duy Nguyen <pclouds@gmail.com>]

On Tue, Apr 4, 2017 at 4:16 AM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> Things I have on my TODO list:

Always keep cache-tree valid. I think there's some changes in "git
checkout" to rebuild cache-tree often, so it's probably not as bad as
before. I don't know if there's a command to manually repair
cache-tree after it's damaged too much (or even better, attempt to
repair cache-tree automatically once damages go over a limit, similar
to how you automatically split index).

> +git status
> +~~~~~~~~~~
> +
> +Running "git status" requires traversing the working tree & comparing
> +it with the index. Several configuration options can help with its
> +performance, with some trade-offs.

Another option, if you know you only make changes in one (preferably
deep) subdirectory and your whole worktree is very large, then you
could do something like "git status .". This speeds git-status up a
bit because it won't need to look outside (or speeds up a lot if
"outside" is very large). The con is, changes outside "." will not be
seen.
-- 
Duy