From: "Gumbel, Matthew K" <matthew.k.gumbel@intel.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: git commit results in many lstat()s
Date: Wed, 1 Feb 2017 21:45:25 +0000 [thread overview]
Message-ID: <DA0A42D68346B1469147552440A645039A9C56D4@ORSMSX115.amr.corp.intel.com> (raw)
Hello,
My high level problem is to speed up git commit on a large repository stored on NFS filesystem. I see via strace that it is slow because it makes a large number (~50,000) of lstat() calls in serial. Every call is a round-trip to the NFS server.
I do not understand why git commit must call lstat() on every file in the repository, even when I specify the name of the file I want to commit on the command line. Can somebody explain why it must call lstat on every file?
My command-line looks like this: git commit -uno -o -m asdf file-to-commit.txt
Secondly, are there any optimizations I can make to avoid this behavior?
Thanks,
Matt
next reply other threads:[~2017-02-01 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 21:45 Gumbel, Matthew K [this message]
2017-02-01 22:11 ` git commit results in many lstat()s Junio C Hamano
2017-02-01 22:26 ` Gumbel, Matthew K
2017-02-01 23:50 ` Junio C Hamano
2017-02-02 0:14 ` Gumbel, Matthew K
2017-02-02 0:25 ` brian m. carlson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DA0A42D68346B1469147552440A645039A9C56D4@ORSMSX115.amr.corp.intel.com \
--to=matthew.k.gumbel@intel.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).