On Sun, Mar 8, 2015 at 12:37 PM, David Kastrup <dak@xxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html