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

Performance regression in git fetch between 1.8.3.4 and 1.8.5.3

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jan 31, 2014, 21:02 UTC
Message-ID
<20140131210154.GA632399@vauxhall.crustytoothpaste.net>

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.

This is an auxiliary repository, so its size is probably between 6-7 GiB. It does not have an especially large number of refs, but is a clone of our main repository.

Other than the new version, the only difference is that 1.8.5.3 is built against libpcre. These are both running on the same CentOS 6 system; literally the only difference is installing one RPM or the other.

1.8.3.4:
  brianc ok # for i in `seq 1 3`; do time git fetch; done
  git fetch  0.86s user 0.18s system 78% cpu 1.314 total
  git fetch  0.88s user 0.19s system 79% cpu 1.348 total
  git fetch  0.84s user 0.18s system 78% cpu 1.299 total
1.8.5.3:
  brianc ok # for i in `seq 1 3`; do time git fetch; done
  git fetch  17.11s user 1.22s system 98% cpu 18.652 total
  git fetch  16.74s user 1.24s system 98% cpu 18.286 total
  git fetch  17.78s user 1.35s system 98% cpu 19.446 total
Does anyone have any idea what might be causing this?
-- 
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
Next: Jeff King
Message 1 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.