git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Performance regression in git fetch between 1.8.3.4 and 1.8.5.3

From
Jeff King <peff@peff.net>
Date
Jan 31, 2014, 21:35 UTC
Message-ID
<20140131213505.GA21264@sigill.intra.peff.net>
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
Previous: brian m. carlsonNext: brian m. carlson
Message 2 of 3 in “Performance regression in git fetch between 1.8.3.4 and 1.8.5.3”
  1. brian m. carlsonJan 31, 2014
  2. Jeff KingJan 31, 2014
  3. brian m. carlsonFeb 1, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.