From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 04 Oct 2012 19:36:38 GMT
Subject: Re: git pull takes ~8 seconds on up-to-date Linux git tree
Message-ID: <7vy5jmxc55.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20121004184314.GA15389@sigill.intra.peff.net>

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.

Thanks; we probably should revert the merge before the final and
handle the fallout later, unless we know why the integrated whole is
slower than its parts.