git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Bryan Turner <bturner@atlassian.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, Git Users <git@vger.kernel.org>
Subject: Re: Simulating network throttling
Date: Wed, 16 Jun 2021 22:57:26 +0000	[thread overview]
Message-ID: <YMqB1mT9yeRCuA/N@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAGyf7-HyUHJacvpwx6R+_hCVsK_t3F1mQ++2_4-NeJWB9uUjdA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1934 bytes --]

On 2021-06-16 at 04:59:00, Bryan Turner wrote:
> On Tue, Jun 15, 2021 at 9:56 PM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> >
> > Hi,
> >
> > I would like to test my Git repository in case the network is throttled
> > (that is the network speed is reduced from its full speed). For example,
> > I would like to test git clone under maximum download speed of 9.6 KB/s
> > (GPRS speed).
> >
> > I know how to test for throttling in browser, but since Git is
> > command-line application, is there any way to simulate network throttling?
> 
> I've had some luck using toxiproxy[1] to MITM the connection, at least
> over plain HTTP. It's worth noting a warning brian m. carlson has
> given others in the past about this sort of thing, though, which is
> that many MITM solutions are not fully transparent, which can result
> in protocol errors and other abnormal behaviors from Git. Your mileage
> may vary.

That is a warning I frequently give, both here and on Stack Overflow,
but I think if you're using a controlled environment and proxying data
just for yourself, the only person you're hurting is you, so I'm not
going to complain about it very much.  It may nevertheless result in
false failures that you'd otherwise want to avoid, though.

On Linux, you can also use the tc command to do traffic shaping and
policing to allow only a certain amount of bandwidth, and you can use it
in conjunction with iptables or nftables to do it only on certain ports
or IPs.  It's very powerful and doesn't suffer from the limitations of
proxies, but it also is rather complicated to set up, so you may want to
try a proxy first to see if it meets your needs with less work.

OpenBSD's (and FreeBSD's, Darwin's, etc.) pf supports the same
functionality but with a much nicer and easier to use interface (and I
say this as a Linux user).
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2021-06-16 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  4:55 Simulating network throttling Bagas Sanjaya
2021-06-16  4:59 ` Bryan Turner
2021-06-16 22:57   ` brian m. carlson [this message]
2021-06-17  7:19     ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YMqB1mT9yeRCuA/N@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=bagasdotme@gmail.com \
    --cc=bturner@atlassian.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).