From: Kevin D <me@ikke.info>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: git@vger.kernel.org
Subject: Re: Git very slow ?
Date: Sun, 8 Mar 2015 16:51:36 +0100 [thread overview]
Message-ID: <20150308155136.GA6273@vps892.directvps.nl> (raw)
In-Reply-To: <20150307013007.GA13250@milliways>
On Sat, Mar 07, 2015 at 01:30:07AM +0000, Ken Moffat wrote:
> Hi, please CC me if that is not your usual fashion, because I am not
> subscribed.
>
> I use git for my build scripts - those are accessed over nfs. Since
> I started using 2.1 and later (I don't think I used 2.0) commands
> such as 'commit' take a long time before anything happens. I
> assumed that the newer version meant this would take longer.
>
> But today^Wyesterday I was bisecting the kernel on a local
> filesystem - even when the number of revisions left to test was in
> the single digits, git bisect took a long time to decide which
> revision should be the next one to test. The filesystems are ext4.
> Is this sort of delay normal now?
>
> What really prompted me to ask is that I ran git blame on a script,
> to see when I made a particular change so that I could add that
> information to a ticket, and almost gave up waiting because it felt
> as if it was taking for ever.
>
What kind of repository are we talking about? How many files, how big?
Git should not have become significantly slower recently.
Also, might there be anti-virus software that slows down file access?
next prev parent reply other threads:[~2015-03-08 15:52 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 [this message]
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
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=20150308155136.GA6273@vps892.directvps.nl \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--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).