From: "Paweł Sikora" <pawel.sikora@agmk•net>
To: Duy Nguyen <pclouds@gmail•com>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: slow git-cherry-pick.
Date: Sun, 24 Nov 2013 20:17:25 +0100 [thread overview]
Message-ID: <32998962.pucYdvRloz@localhost.localdomain> (raw)
In-Reply-To: <CACsJy8CAAov1nSGPx79U+md4xROsCydidHPcipOb_sdFwNdSkA@mail.gmail.com>
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?
> Do you cherry-pick on one commit or a commit range?
single commit.
--
gpg key fingerprint = 60B4 9886 AD53 EB3E 88BB 1EB5 C52E D01B 683B 9411
next prev parent reply other threads:[~2013-11-24 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 10:45 slow git-cherry-pick Paweł Sikora
2013-11-24 12:47 ` Duy Nguyen
2013-11-24 12:48 ` Duy Nguyen
2013-11-24 19:17 ` Paweł Sikora [this message]
2013-11-25 17:26 ` Junio C Hamano
2013-12-03 19:31 ` Paweł Sikora
2013-12-03 20:13 ` Thomas Rast
2013-12-04 1:07 ` Duy Nguyen
2013-12-04 12:46 ` Paweł Sikora
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=32998962.pucYdvRloz@localhost.localdomain \
--to=pawel.sikora@agmk$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=pclouds@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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