From: Jeff King <peff@peff.net>
To: Andrew Cameron <andrew@worksmartlabs.com>
Cc: git@vger.kernel.org
Subject: Re: git checkout running very slowly (>12s)
Date: Mon, 20 Jun 2011 20:44:52 -0400 [thread overview]
Message-ID: <20110621004452.GA3064@sigill.intra.peff.net> (raw)
In-Reply-To: <loom.20110620T221426-685@post.gmane.org>
On Mon, Jun 20, 2011 at 08:26:37PM +0000, Andrew Cameron wrote:
> In other words, it appears that an efficient lstat implementation was not the
> key factor in this problem. The root cause remains a mystery, but in my case,
> the solution was to upgrade Git.
If you can reliably trigger the problem by switching versions and you
are still curious and want to spend a little more time on it, you may be
able to bisect the fix to solve the mystery.
Keep in mind that you are bisecting a fix, not a regression, so your
meanings of "good" and "bad" will be opposite of what you expect. I.e.,
"bad" commits will have the fix, and "good" commits will not (I know
this is confusing; it's an artifact of the way bisect works).
-Peff
next prev parent reply other threads:[~2011-06-21 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 19:30 git checkout running very slowly (>12s) Andrew Cameron
2011-06-15 22:46 ` Andreas Ericsson
2011-06-15 23:16 ` Andrew Cameron
2011-06-20 20:26 ` Andrew Cameron
2011-06-21 0:44 ` Jeff King [this message]
2011-06-21 14:34 ` Jeff King
2011-06-21 14:44 ` Andrew Cameron
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=20110621004452.GA3064@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=andrew@worksmartlabs.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).