From: Pascal Obry <pascal@obry.net>
To: Jon Nelson <jnelson@jamponi.net>
Cc: git@vger.kernel.org
Subject: Re: git-svn and *lots* of ssh connections
Date: Thu, 11 Jun 2009 09:52:02 +0200 [thread overview]
Message-ID: <4A30B7A2.709@obry.net> (raw)
In-Reply-To: <cccedfc60906100709r18364bc2h82d8e1a7ee0b8fd1@mail.gmail.com>
Jon Nelson a écrit :
> 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 don't know if git-svn can be improved but I would go with a reusable
ssh connection (this is not working with Cygwin though).
See for example (but lot of web site talk about this):
http://www.cyberciti.biz/faq/linux-unix-reuse-openssh-connection/
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net - http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B
next prev parent reply other threads:[~2009-06-11 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 14:09 git-svn and *lots* of ssh connections Jon Nelson
2009-06-11 7:52 ` Pascal Obry [this message]
2009-06-25 9:49 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A30B7A2.709@obry.net \
--to=pascal@obry.net \
--cc=git@vger.kernel.org \
--cc=jnelson@jamponi.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).