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

Re: git-fetch takes forever on a slow network link. Can parallel mode help?

From
RDR. Diez <rdiez-2006@rd10.de>
Date
Mar 11, 2026, 18:05 UTC
Message-ID
<d7b6defb-1614-40e6-b46b-a36d71388431@rd10.de>
In-Reply-To
<abCgUu3ZFSOIZwKu@fruit.crustytoothpaste.net>
> Git doesn't use standard SSH file transfer operations.
> [...]
OK, thanks for the information.
I have finally done a "git gc" on the server side, and now a "git pull" from the client with no new commits to download takes 4 seconds, a drastic reduction from the 25 seconds it took before.
I turns out I hadn't done a "git gc" on the server for over 2 years, so that many new references weren't packed.
Therefore, I think that having many small files to read versus one packed-refs file makes a huge difference if you have mounted a remote filesystem over a network with a relatively high latency.
My 1 Mbps connection does not actually have such a high latency (around 40 ms measured with ping), but latency seems to have a much greater impact than the low bandwidth, at least with a packed-refs file which only weighs 64 kB.
Best regards,
   rdiez
Previous: brian m. carlson
Message 9 of 9 in “git-fetch takes forever on a slow network link. Can parallel mode help?”
  1. R. DiezMar 6, 2026
  2. brian m. carlsonMar 6, 2026
  3. R. DiezMar 7, 2026
  4. brian m. carlsonMar 8, 2026
  5. R. DiezMar 8, 2026
  6. brian m. carlsonMar 8, 2026
  7. R. DiezMar 9, 2026
  8. brian m. carlsonMar 10, 2026
  9. R. DiezMar 11, 2026

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.