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

git-svn and *lots* of ssh connections

From
JNJon Nelson <jnelson@jamponi.net>
Date
Jun 10, 2009, 14:09 UTC
Message-ID
<cccedfc60906100709r18364bc2h82d8e1a7ee0b8fd1@mail.gmail.com>

The company I work for (but do not speak for) uses svn (via ssh). I tried to use it; I really did. But I missed git and found svn quite honestly painful to use so I went to git-svn, and other than some caveats I'm pretty happy. However, one of the issues I've had with git-svn is fairly troublesome.

Basically, during the fetch stage (or clone) git-svn uses a *ton* of ssh connections. Many dozens and in even with smaller projects well over a hundred. By "small" I mean a .git of less than 6MB and less than 60 files in the checkout. I've got 4MBit bandwidth available but frequently see only a single digit fraction of that going to the fetch/clone process. Is there anything that can be done to reduce the number of ssh connections involved? Why can't a single connection simple be re-used? I can't use "ssh connection sharing" for a variety of reasons that aren't relevant here.

I'm using 1.6.0.2.
-- 
Jon
Next: Pascal Obry
Message 1 of 3 in “git-svn and *lots* of ssh connections”
  1. Jon NelsonJun 10, 2009
  2. Pascal ObryJun 11, 2009
  3. Eric WongJun 25, 2009

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.