From: "Paweł Sikora" <pawel.sikora@agmk.net>
To: git@vger.kernel.org
Subject: slow git-cherry-pick.
Date: Sun, 24 Nov 2013 11:45:32 +0100 [thread overview]
Message-ID: <2142926.gg3W3MsbJZ@localhost.localdomain> (raw)
Hi,
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.
my git repo isn't very big[1] but it's checked out on the linear lvm
where random i/o generally hurts and strace shows that current git version
performs 2x{lstat}+1x{open,read,close} [2] on whole checkout before
cherry-pick. there is also a .gitattributes searching on all levels
which doing another tons of i/o. looks like git-status on action but
why on whole repo while cherry-pick touches limited set of files?
is it a bug or feature?
BR,
Paweł.
please CC me on reply.
[1]
$ du -sh .git/objects/
4.2G .git/objects/
$ find sources -type f|wc -l
9536
$ find buildenv -type f|wc -l
14637
[2]
lstat("buildenv/boost-1.51.0/include/boost/bimap.hpp", {st_mode=S_IFREG|0664,
st_size=387, ...}) = 0
lstat("buildenv/boost-1.51.0/include/boost/bimap.hpp", {st_mode=S_IFREG|0664,
st_size=387, ...}) = 0
open("buildenv/boost-1.51.0/include/boost/bimap.hpp", O_RDONLY) = 5
read(5, "// Boost.Bimap\n//\n// Copyright ("..., 387) = 387
close(5)
--
gpg key fingerprint = 60B4 9886 AD53 EB3E 88BB 1EB5 C52E D01B 683B 9411
next reply other threads:[~2013-11-24 11:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 10:45 Paweł Sikora [this message]
2013-11-24 12:47 ` slow git-cherry-pick Duy Nguyen
2013-11-24 12:48 ` Duy Nguyen
2013-11-24 19:17 ` Paweł Sikora
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=2142926.gg3W3MsbJZ@localhost.localdomain \
--to=pawel.sikora@agmk.net \
--cc=git@vger.kernel.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).