From: Ralph Seichter <git-ml@seichter.de>
To: git@vger.kernel.org
Subject: How to limit bandwidth used by git over SSH ?
Date: Sun, 17 Jul 2011 12:22:47 +0200 [thread overview]
Message-ID: <4E22B7F7.4020701@seichter.de> (raw)
Hello list,
I'm not really sure if this is a git or SSH issue, but I haven't figured
out a solution yet. To transfer my data between two machines, I use
git-push ssh://machineB.tld/foo/proj.git master
from machineA. Unfortunately, the machines are connected by a very low-
bandwidth connection, which is completely choked by git-push. From what
I've read so far, I guess this is the result of SSH setting TOS to
"minimize delay", which prevents almost all other traffic during the
push operation. Not good.
I haven't yet found a way of telling git (or SSH) to use no more than a
given maximum bandwidth, like I could do with "scp -l {limit}". Did I
miss something in the documentation?
Your help is appreciated.
-Ralph
next reply other threads:[~2011-07-17 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 10:22 Ralph Seichter [this message]
2011-07-19 8:42 ` How to limit bandwidth used by git over SSH ? Carlos Martín Nieto
2011-07-20 19:18 ` Ralph Seichter
2011-07-20 20:20 ` Andreas Krey
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=4E22B7F7.4020701@seichter.de \
--to=git-ml@seichter.de \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.