From: Dun Peal <dunpealer@gmail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: Inexplicably deteriorating performance of Git repositories on Windows
Date: Wed, 24 Nov 2010 20:10:40 +0000 [thread overview]
Message-ID: <AANLkTim9hvekD0VmYdM2YfyGCqPe71yHv9PxsvnbNnR0@mail.gmail.com> (raw)
In-Reply-To: <4CECF837.1080404@op5.se>
On Wed, Nov 24, 2010 at 11:34 AM, Andreas Ericsson <ae@op5.se> wrote:
> How many refs (tags and branches) do you have?
We have about 15 branches, but thousands of tags (we tag each release,
and we make those often). However, I'm not sure how that could make
`git status` slow, since it shouldn't care about tags at all?
> Are the refs packed or loose?
Packed.
> If they are loose, does packing them resolve the issue?
> Are you using network-mounted or local storage?
Local storage on all workstations. One machine with those performance
issues actually utilizes an incredibly fast, cutting edge SSD. It's
twice as fast as the other slow machine, but 8s for `git status` is
still slow.
> What does the .git/config file look like for a user where git status
> is excruciatingly slow?
It's the normal .git/config you get by default on Git 1.7.x when
cloning from a remote. I can paste it if you want, but doubt it will
interest anyone: we didn't modify it.
> Does copying the config file from a windows user to a linux user make
> timings somewhat consistent between various systems?
No.
> Do older version of git perform as poorly?
Yes.
> How is the repository laid out (ie, are there any directories with
> a ton of files in, or are they spread across multiple directories)?
Generally spread across multiple directories.
> How many .gitignore files are you using, and what do they look like?
We're using 25 of those,
>> 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.
Yes, it's weird. I'm not sure it's a "system" issue since we're seeing
it across a diverse set of Windows systems: Vista, Windows 7, pretty
sure I saw XP as well, different hardware and software setups
(different programs installed and running).
.D
next prev parent reply other threads:[~2010-11-24 20:14 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
2010-11-24 20:10 ` Dun Peal [this message]
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=AANLkTim9hvekD0VmYdM2YfyGCqPe71yHv9PxsvnbNnR0@mail.gmail.com \
--to=dunpealer@gmail.com \
--cc=ae@op5.se \
--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).