From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Kastrup <dak@gnu.org>
Cc: Ken Moffat <zarniwhoop@ntlworld.com>, Kevin D <me@ikke.info>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Git very slow ?
Date: Sun, 8 Mar 2015 12:46:07 -0700 [thread overview]
Message-ID: <CA+55aFzDRg4kHHGGHd91kVxfj8eX0g1w5T7SyN_CouCf=_tW3A@mail.gmail.com> (raw)
In-Reply-To: <87sidfmgag.fsf@fencepost.gnu.org>
On Sun, Mar 8, 2015 at 12:37 PM, David Kastrup <dak@gnu.org> wrote:
>
> Since git blame outputs everything once it is finished ("the first
> screen" is purely the pager's business), it needs to unpack the entire
> history of the file (unless no blameable lines remain at all) and look
> at it. 6 seconds tends not to be all that excessive for extracting more
> than 5 years of a file's history.
Yeah, "git blame" can easily be several seconds without anything being wrong.
But "git commit" should be fairly instantaneous. Even over NFS.
That said, on NFS in particular, make sure you don't have
[core]
PreloadIndex = false
in your .gitconfig to disable the threaded index preloading.
But "core.preloadindex" _should_ be enabled by default in anything but
the most ancient git versions, and it can make a huge difference on
NFS because it allows the 'lstat()' calls to check that the index is
up-to-date to be done in parallel. Without that, git on NFS can be a
bit sluggish.
On local filesystems it normally doesn't make as much of a difference,
since things tend to be either cached or seek-limited.
Linus
next prev parent reply other threads:[~2015-03-08 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 1:30 Git very slow ? Ken Moffat
2015-03-08 15:51 ` Kevin D
2015-03-08 16:21 ` David Kastrup
2015-03-08 19:20 ` Ken Moffat
2015-03-08 19:37 ` David Kastrup
2015-03-08 19:46 ` Linus Torvalds [this message]
2015-03-08 19:02 ` Ken Moffat
2015-03-08 19:39 ` Linus Torvalds
2015-03-08 23:31 ` Ken Moffat
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='CA+55aFzDRg4kHHGGHd91kVxfj8eX0g1w5T7SyN_CouCf=_tW3A@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=me@ikke.info \
--cc=zarniwhoop@ntlworld.com \
/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).