From: Joshua Jensen <jjensen@workspacewhiz.com>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Dun Peal <dunpealer@gmail.com>,
Wilbert van Dolleweerd <wilbert@arentheym.com>,
Git ML <git@vger.kernel.org>
Subject: Re: Inexplicably deteriorating performance of Git repositories on Windows
Date: Wed, 24 Nov 2010 10:16:58 -0700 [thread overview]
Message-ID: <4CED488A.2070507@workspacewhiz.com> (raw)
In-Reply-To: <AANLkTim-1uKTVacr1N=9bhZ+=ngggrJS=GD-YNjkSuBR@mail.gmail.com>
----- Original Message -----
From: Tay Ray Chuan
Date: 11/24/2010 7:16 AM
> On Wed, Nov 24, 2010 at 3:59 AM, Dun Peal<dunpealer@gmail.com> wrote:
>> On Tue, Nov 23, 2010 at 7:12 PM, Wilbert van Dolleweerd
>> <wilbert@arentheym.com> wrote:
>> The working copy totals about 4GB. The .git directory, tightly
>> packed, is 1GB.
> What does the structure of your working tree look like? I think the
> depth might be affecting performance
Whenever I want to know exactly what is going on with disk access, I
download Process Monitor from http://sysinternals.com/.
In order to just show disk access, I filter entries that begin with TCP,
UDP, and Reg out.
Josh
next prev parent reply other threads:[~2010-11-24 17:17 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 [this message]
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
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=4CED488A.2070507@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--cc=dunpealer@gmail.com \
--cc=git@vger.kernel.org \
--cc=rctay89@gmail.com \
--cc=wilbert@arentheym.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.