git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Dun Peal <dunpealer@gmail.com>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: Inexplicably deteriorating performance of Git repositories on Windows
Date: Wed, 24 Nov 2010 12:34:15 +0100	[thread overview]
Message-ID: <4CECF837.1080404@op5.se> (raw)
In-Reply-To: <AANLkTimTh7ka21inpovM=qqdWs6j2OcPXVsFh_CMiZ7N@mail.gmail.com>

On 11/23/2010 08:08 PM, Dun Peal wrote:
> 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.

  parent reply	other threads:[~2010-11-24 11:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 19:08 Inexplicably deteriorating performance of Git repositories on Windows Dun Peal
2010-11-23 19:12 ` Wilbert van Dolleweerd
2010-11-23 19:59   ` Dun Peal
2010-11-23 20:10     ` Wilbert van Dolleweerd
2010-11-23 20:25     ` Stephen Bash
2010-11-23 21:07       ` Dun Peal
2010-11-24 14:16     ` Tay Ray Chuan
2010-11-24 17:16       ` Joshua Jensen
2010-11-24 21:00         ` Dun Peal
2010-11-24 21:18           ` A Large Angry SCM
2010-11-24 22:06           ` Johannes Sixt
2010-11-24 20:48       ` Dun Peal
2010-11-23 21:13 ` Martin Langhoff
2010-11-23 21:17   ` Dun Peal
2010-11-23 21:49 ` Ferry Huberts
2010-11-23 23:23   ` Dun Peal
2010-11-24 11:34 ` Andreas Ericsson [this message]
2010-11-24 20:10   ` Dun Peal
2010-11-24 13:32 ` Nguyen Thai Ngoc Duy
2010-11-24 20:22   ` Dun Peal
2010-11-28 22:18 ` Robin Rosenberg

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=4CECF837.1080404@op5.se \
    --to=ae@op5.se \
    --cc=dunpealer@gmail.com \
    --cc=git@vger.kernel.org \
    /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).