From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: Re: Performance regression in git fetch between 1.8.3.4 and 1.8.5.3
Date: Fri, 31 Jan 2014 16:35:05 -0500 [thread overview]
Message-ID: <20140131213505.GA21264@sigill.intra.peff.net> (raw)
In-Reply-To: <20140131210154.GA632399@vauxhall.crustytoothpaste.net>
On Fri, Jan 31, 2014 at 09:02:15PM +0000, brian m. carlson wrote:
> At work, we recently upgraded our git version from 1.8.3.4 to 1.8.5.3.
> We've noticed a significant performance regression in git fetch. The
> numbers below are for an up-to-date branch (that is, no data is actually
> being fetched) for a git-over-ssh remote on our gitorious server.
Is it better with v1.9-rc1? There was a slowdown in v1.8.4.2 that I
addressed with commit 200abe7 (which is slated for v1.9).
-Peff
next prev parent reply other threads:[~2014-01-31 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 21:02 Performance regression in git fetch between 1.8.3.4 and 1.8.5.3 brian m. carlson
2014-01-31 21:35 ` Jeff King [this message]
2014-02-01 0:41 ` brian m. carlson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140131213505.GA21264@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).