Re: Inexplicably deteriorating performance of Git repositories on Windows

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Nov 24, 2010, 13:32 UTC
Message-ID: <AANLkTinTisPh-x-JQBMkz-b=RoMJ6PUQ8Hp1VV_uZ=V+@mail.gmail.com>
In-Reply-To: <AANLkTimTh7ka21inpovM=qqdWs6j2OcPXVsFh_CMiZ7N@mail.gmail.com>

On Wed, Nov 24, 2010 at 2:08 AM, Dun Peal <dunpealer@gmail.com> wrote:

Show 15 quoted lines

> Hey,
>
> We have a bunch of Windows users, unfortunately, and they're using the
> latest msysGit release (Git-1.7.3.1-preview20101002).
>
> An interesting issue we've noticed is that the Time To Complete of
> their common operations start deteriorating inexplicably, and
> severely, some time after the clone.
>
> For instance, immediately after a clone, `git status` takes about
> 5-6s. Which is slow compared to Linux (consistent 1-2s), but still
> usable (it's a BIG repo).
>
> However, after a reboot (of all things), `git status` latency
> skyrockets to 14-15s, making the repo unusable.

Does assume-unchanged bit (see "git update-index") help? I'm not suggesting to use it but it would help determine if the slowdown is worktree-related.

-- 
Duy