From: Russell King <rmk@arm.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: Is cogito really this inefficient
Date: Thu, 14 Jul 2005 08:37:00 +0100 [thread overview]
Message-ID: <20050714083700.A26322@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0507131325170.17536@g5.osdl.org>; from torvalds@osdl.org on Wed, Jul 13, 2005 at 01:28:18PM -0700
On Wed, Jul 13, 2005 at 01:28:18PM -0700, Linus Torvalds wrote:
> On Wed, 13 Jul 2005, Russell King wrote:
> > This says it all. 1min 22secs to generate a patch from a locally
> > modified but uncommitted file.
>
> No, there's something else going on.
>
> Most likely that something forced a total index file re-validation, and
> the time you see is every single checked out file having its SHA1
> re-computed.
>
> Was this a recently cloned tree, or what was the last operation you did on
> that tree before that command? Something must have invalidated the index.
cg-update origin
and then I edited drivers/serial/8250.c
As discovered using:
sh -x /usr/bin/cg-diff drivers/serial/8250.c
it appears that cg-diff does a
git-update-cache --refresh >/dev/null
each time it's run, which is taking the bulk of the time. Also note
that curiously, it exits with status 1.
--
Russell King
next prev parent reply other threads:[~2005-07-14 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 12:50 Is cogito really this inefficient Russell King
2005-07-13 16:51 ` Matthias Urlichs
2005-07-14 7:38 ` Russell King
2005-07-13 20:28 ` Linus Torvalds
2005-07-14 7:37 ` Russell King [this message]
2005-07-14 9:08 ` Catalin Marinas
2005-07-14 9:59 ` Russell King
2005-07-14 15:51 ` Linus Torvalds
2005-07-15 0:29 ` Linus Torvalds
2005-07-15 2:10 ` Junio C Hamano
2005-07-15 9:48 ` Russell King
2005-07-14 15:26 ` Linus Torvalds
2005-07-19 23:54 ` Petr Baudis
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=20050714083700.A26322@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).