Re: Inexplicably deteriorating performance of Git repositories on Windows

From: Andreas Ericsson <ae@op5.se>
Date: Nov 24, 2010, 11:34 UTC
Message-ID: <4CECF837.1080404@op5.se>
In-Reply-To: <AANLkTimTh7ka21inpovM=qqdWs6j2OcPXVsFh_CMiZ7N@mail.gmail.com>

On 11/23/2010 08:08 PM, Dun Peal wrote:

Show 13 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).
>

How many refs (tags and branches) do you have? Are the refs packed or loose? If they are loose, does packing them resolve the issue? Are you using network-mounted or local storage? What does the .git/config file look like for a user where git status is excruciatingly slow? Does copying the config file from a windows user to a linux user make timings somewhat consistent between various systems? Do older version of git perform as poorly? How is the repository laid out (ie, are there any directories with a ton of files in, or are they spread across multiple directories)? How many .gitignore files are you using, and what do they look like?

> However, after a reboot (of all things), `git status` latency
> skyrockets to 14-15s, making the repo unusable.
>

That's just plain weird, and is almost certainly a system issue.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.