From: <steve.norman@thomsonreuters.com>
To: <peff@peff.net>, <pclouds@gmail.com>
Cc: <junio@pobox.com>, <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.5.0-rc0
Date: Fri, 26 Jun 2015 09:36:04 +0000 [thread overview]
Message-ID: <7FAE15F0A93C0144AD8B5FBD584E1C55197CF80F@C111KJZHMBX55.ERF.thomson.com> (raw)
In-Reply-To: <xmqqr3ozy1zt.fsf@gitster.dls.corp.google.com>
Jeff / Duy,
> Fixes since v2.4
> * Access to objects in repositories that borrow from another one on a
> slow NFS server unnecessarily got more expensive due to recent code
> becoming more cautious in a naive way not to lose objects to pruning.
> (merge ee1c6c3 jk/prune-mtime later to maint).
>
> * "Have we lost a race with competing repack?" check was too
> expensive, especially while receiving a huge object transfer
> that runs index-pack (e.g. "clone" or "fetch").
> (merge 0eeb077 jk/index-pack-reduce-recheck later to maint).
I was reading through the 2.5 release notes and spotted the above two entries and I think they are probably fixes related to the NFS slowness I reported last month.
Did some tests this morning and things are much improved:
Version 2.4.5
- Local clone of https://github.com/git/git - 8s
- Clone to NFS - 1m 3s
Version 2.5.0.rc0
- Local - 7s
- NFS - 13s
Thanks for the effort in addressing this and sorry I missed the patch to check it out earlier.
Steve
next prev parent reply other threads:[~2015-06-26 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 20:19 [ANNOUNCE] Git v2.5.0-rc0 Junio C Hamano
2015-06-26 9:36 ` steve.norman [this message]
2015-06-26 11:20 ` Jeff King
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=7FAE15F0A93C0144AD8B5FBD584E1C55197CF80F@C111KJZHMBX55.ERF.thomson.com \
--to=steve.norman@thomsonreuters.com \
--cc=git@vger.kernel.org \
--cc=junio@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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).