Re: Performance regression in git fetch between 1.8.3.4 and 1.8.5.3

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Feb 1, 2014, 00:41 UTC
Message-ID: <20140201004128.GA635004@vauxhall.crustytoothpaste.net>
In-Reply-To: <20140131213505.GA21264@sigill.intra.peff.net>

On Fri, Jan 31, 2014 at 04:35:05PM -0500, Jeff King wrote:

Show 9 quoted lines

> 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).

Yes.  The time is much lower with 1.9-rc1:

  brianc ok # for i in `seq 1 3`; do time git fetch; done
  git fetch  0.90s user 0.18s system 74% cpu 1.447 total
  git fetch  0.88s user 0.20s system 74% cpu 1.456 total
  git fetch  0.88s user 0.19s system 74% cpu 1.438 total

I'll open a case to get it updated once 1.9 is finally released. Thanks for your suggestion.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187