Re: slow git-cherry-pick.

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 25, 2013, 17:26 UTC
Message-ID: <xmqqd2loz92n.fsf@gitster.dls.corp.google.com>
In-Reply-To: <32998962.pucYdvRloz@localhost.localdomain>

Paweł Sikora <pawel.sikora@agmk.net> writes:

Show 21 quoted lines

> On Sunday 24 of November 2013 19:47:10 Duy Nguyen wrote:
>> On Sun, Nov 24, 2013 at 5:45 PM, Paweł Sikora <pawel.sikora@agmk.net> wrote:
>> > i've recently reinstalled a fresh system (fc20-beta) on my workstation
>> > and observing a big slowdown on git cherry-pick operation (git-1.8.4.2-1).
>> > the previous centos installation with an old git version works faster
>> > (few seconds per cherry pick). now the same operation takes >1 min.
>> 
>> What is the git version before the reinstallation?
>
> git-1.7.11.3-1.el5.rf.
>
> i've checked this version on another machine with centos-5.$latest
> and it does similar amout of stat/read operation quickly (~6s).
> this "fast" centos-5 machine has /home on raid-0 (2x500GB) while
> my "slow (>1min)" workstation has /home on linear lvm (250G+1T).
>
> so, i suppose that my "slow" working copy crosses disks boundary
> or spread over 1TB drive and the random git i/o impacts performance.
>
> the question still remains - does the git need to scan whole checkout
> during picking well defined set of files?

We do update-index to see what local changes you have upfront in order to avoid stomping on them (and we do not know upfront what paths the cherry-picked commit would change, given that there may be renames involved), so the answer is unfortunately yes, we would need to do lstat(2) the whole thing.

Doing that lstat(2) more lazily and do away with the update-index might be possible, but I suspect that may be quite a lot of work.