From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>, git@vger.kernel.org
Subject: Re: git pull takes ~8 seconds on up-to-date Linux git tree
Date: Thu, 04 Oct 2012 14:28:11 -0700 [thread overview]
Message-ID: <7vvceqvses.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7v391ux7im.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 04 Oct 2012 14:16:33 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Jeff King <peff@peff.net> writes:
>
>> On Thu, Oct 04, 2012 at 04:14:54PM +0200, Markus Trippelsdorf wrote:
>>
>>> with current trunk I get the following on an up-to-date Linux tree:
>>>
>>> markus@x4 linux % time git pull
>>> Already up-to-date.
>>> git pull 7.84s user 0.26s system 92% cpu 8.743 total
>>>
>>> git version 1.7.12 is much quicker:
>>>
>>> markus@x4 linux % time git pull
>>> Already up-to-date.
>>> git pull 0.10s user 0.02s system 16% cpu 0.740 total
>>
>> Yikes. I can easily reproduce here. Bisecting between master and
>> v1.7.12 gives a curious result: the slowdown first occurs with the merge
>> commit 34f5130 (Merge branch 'jc/merge-bases', 2012-09-11). But neither
>> of its parents is slow. I don't see anything obviously suspect in the
>> merge, though.
>
> I think the following is likely to be the correct solution to this.
No, it is not. Sorry for the noise.
next prev parent reply other threads:[~2012-10-04 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 14:14 git pull takes ~8 seconds on up-to-date Linux git tree Markus Trippelsdorf
2012-10-04 18:43 ` Jeff King
2012-10-04 19:26 ` Markus Trippelsdorf
2012-10-04 19:36 ` Junio C Hamano
2012-10-04 20:03 ` Junio C Hamano
2012-10-04 20:44 ` Junio C Hamano
2012-10-04 21:16 ` Junio C Hamano
2012-10-04 21:28 ` Junio C Hamano [this message]
2012-10-04 22:37 ` Junio C Hamano
2012-10-05 20:34 ` Junio C Hamano
2012-10-05 23:21 ` Jeff King
2012-10-06 5:20 ` Junio C Hamano
2012-10-06 12:57 ` Jeff King
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=7vvceqvses.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=peff@peff.net \
/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).