From: David Kastrup <dak@gnu.org>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: Kevin D <me@ikke.info>, git@vger.kernel.org
Subject: Re: Git very slow ?
Date: Sun, 08 Mar 2015 20:37:43 +0100 [thread overview]
Message-ID: <87sidfmgag.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20150308192045.GB32504@milliways> (Ken Moffat's message of "Sun, 8 Mar 2015 19:20:46 +0000")
Ken Moffat <zarniwhoop@ntlworld.com> writes:
> On Sun, Mar 08, 2015 at 05:21:22PM +0100, David Kastrup wrote:
>
>> Particularly not git-blame in 2.1. I should be quite surprised to see
>> any git-blame call running noticeably slower in 2.1 than in any
>> preceding version.
>>
>> What may have happened is that the repository recently got repacked
>> aggressively and thus any access to older revisions got slower.
>> However, that change would be mostly tied to the repository rather than
>> the version of Git you access it with.
>>
> That is possible - well, not recently-recently, but I might have
> repacked my repo of buildscripts some time last year. Running
> ls -al .git
> in that repository gives me:
> drwxr-xr-x 8 ken 100 4096 Mar 8 16:08 .
> drwxr-xr-x 48 ken 100 4096 Mar 8 03:05 ..
> -rw-r--r-- 1 ken 100 220 May 12 2014 BRANCH_DESCRIPTION
> drwxr-xr-x 2 ken 100 4096 Apr 13 2010 branches
> -rw-r--r-- 1 ken 100 470 Mar 8 16:08 COMMIT_EDITMSG
> -rw-r--r-- 1 ken 100 566 May 17 2014 config
> -rw-r--r-- 1 ken 100 73 May 1 2010 description
> -rw-r--r-- 1 ken 100 196439 Sep 17 21:56 gitk.cache
> -rw-rw-rw- 1 ken 100 29 Feb 8 22:19 HEAD
> drwxr-xr-x 2 ken 100 4096 May 1 2010 hooks
> -rw-r--r-- 1 ken 100 218255 Mar 8 16:07 index
> drwxr-xr-x 2 ken 100 4096 Sep 16 2013 info
> drwxr-xr-x 3 ken 100 4096 Sep 16 2013 logs
> drwxr-xr-x 260 ken 100 4096 Nov 12 2013 objects
> -rw-r--r-- 1 ken 100 41 Nov 11 06:05 ORIG_HEAD
> -rw-r--r-- 1 ken 100 1879 Sep 16 2013 packed-refs
> drwxr-xr-x 5 ken 100 4096 May 20 2014 refs
> -rw-r--r-- 1 ken 100 41 Dec 7 2010 RENAMED-REF
>
> Running git blame on a script which dates back to when the repo was
> created takes between 5 and 6 seconds to show the first screen,
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.
--
David Kastrup
next prev parent reply other threads:[~2015-03-08 19:39 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 [this message]
2015-03-08 19:46 ` Linus Torvalds
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=87sidfmgag.fsf@fencepost.gnu.org \
--to=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).