From: Andy Furniss <adf.lists@gmail.com>
To: Dendari Marini <dendari92@gmail.com>,
Benjamin Cronce <bcronce@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Getting Cake to work better with Steam and similar applications
Date: Mon, 1 May 2017 12:32:38 +0100 [thread overview]
Message-ID: <8d2720cb-fd26-0ed8-5e59-c9a062384966@gmail.com> (raw)
In-Reply-To: <CANCX+3NuFPuv_OCtrTP5prmD+z63N=JTFGE2RtREWm2VNQnRzw@mail.gmail.com>
Dendari Marini wrote:
>> What's your RTT(ping) to the different services, like Steam and
>> Windows Update? Some ISPs have local CDNs that can give incredibly
>> low latency relative to the provisioned bandwidth, which can cause
>> bad things to happen with TCP.
> I tried Battle.net and Steam (manually starting a Windows Update is
> rather difficult) and it seems Battle.net servers are closer
> compared to the Steam ones (and as I said I don't have the same
> issues with Battle.net).
Well it seems distance is important for BBR. It seems to have a design
whereby your rtt to the server determines how badly it will bork your
latency. Unlike cubic it doesn't take loss/ecn as a hint to get out of
its exponential phase, which is IMHO not a friendly thing to do, I mean
didn't they think people have to share connections :-(
Playing with a sim, something like dash that grabs a meg waits then gets
another with a new connection needs crazy amount of back off to avoid
borking latency every chunk. The amount of disruption getting worse the
higher the RTT of the TCP.
If you don't have a close CDN plus a low latency DSL gaming is not going
to be nice sharing with repeatedly starting up bbr.
With constant download muti-thread sims - like steam, there is sometimes
a case where every 10 seconds there will be a spike as bbr does probes.
This doesn't happen as much with staggered starts for the TCPs. It does
happen with single connections.
By default cake uses rtt parameter of 100ms - this seems to cause
excessive drops/marks causing upstream bandwidth issues on a connection
like yours. Increasing to say 300 reduces drops/marks but does make some
latency spikes a bit worse.
In summary BBR if you are not close to the server is a nightmare to
shape for latency on ingress. I am testing with 40ms rtt, which I don't
thing is excessive. Where I live, luckily youtube/steam are only 8ms and
things are a lot nicer when emulating that.
next prev parent reply other threads:[~2017-05-01 11:32 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 13:39 Dendari Marini
2017-04-20 13:43 ` Sebastian Moeller
2017-04-20 15:23 ` Dendari Marini
2017-04-20 15:32 ` Jonathan Morton
2017-04-20 16:05 ` Dendari Marini
2017-04-20 17:12 ` Andy Furniss
2017-04-20 17:36 ` Jonathan Morton
2017-04-20 18:35 ` Sebastian Moeller
2017-04-20 18:36 ` Sebastian Moeller
2017-04-21 8:34 ` Dendari Marini
2017-04-21 13:25 ` Sebastian Moeller
2017-04-21 13:27 ` Dendari Marini
2017-04-22 8:25 ` Dendari Marini
2017-04-22 9:36 ` Jonathan Morton
2017-04-22 12:50 ` xnoreq
2017-04-22 13:41 ` Tristan Seligmann
2017-04-22 13:51 ` Andy Furniss
2017-04-22 14:03 ` Andy Furniss
2017-04-22 16:38 ` Andy Furniss
2017-04-22 16:45 ` Dave Taht
2017-04-22 17:00 ` Tristan Seligmann
2017-04-22 20:24 ` Andy Furniss
2017-04-22 16:47 ` Sebastian Moeller
2017-04-22 21:56 ` Dendari Marini
2017-04-22 22:15 ` Sebastian Moeller
2017-04-23 12:32 ` David Lang
2017-04-24 7:55 ` Sebastian Moeller
2017-04-24 8:41 ` Dendari Marini
2017-04-24 11:34 ` Sebastian Moeller
2017-04-24 12:08 ` Dendari Marini
2017-04-24 12:35 ` Sebastian Moeller
2017-04-24 13:49 ` Dendari Marini
2017-04-24 15:42 ` Sebastian Moeller
2017-04-24 17:32 ` Sebastian Moeller
2017-04-25 10:26 ` Andy Furniss
2017-04-25 11:24 ` Dendari Marini
2017-04-25 12:58 ` Andy Furniss
2017-04-25 18:22 ` Dendari Marini
2017-04-25 19:10 ` Jonathan Morton
2017-04-25 20:44 ` Dendari Marini
2017-04-25 21:32 ` Andy Furniss
2017-04-25 22:33 ` Benjamin Cronce
2017-04-28 15:37 ` Dendari Marini
2017-04-29 15:11 ` Andy Furniss
2017-04-29 17:30 ` Jonathan Morton
2017-04-29 18:29 ` Andy Furniss
2017-04-30 0:05 ` Andy Furniss
2017-05-01 5:50 ` Jonathan Morton
2017-05-01 11:32 ` Andy Furniss [this message]
2017-05-01 12:08 ` Jonathan Morton
2017-05-01 13:03 ` Andy Furniss
2017-05-01 13:11 ` Jonathan Morton
2017-05-01 14:46 ` Andy Furniss
2017-04-25 21:06 ` Andy Furniss
2017-04-25 21:16 ` Neil Shepperd
2017-04-25 21:37 ` Andy Furniss
2017-04-25 21:43 ` Sebastian Moeller
2017-04-25 22:06 ` Andy Furniss
2017-04-25 22:29 ` Andy Furniss
2017-04-25 22:32 ` Andy Furniss
2017-04-22 22:35 ` Andy Furniss
2017-04-22 14:12 ` Sebastian Moeller
2017-04-20 18:16 ` Sebastian Moeller
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: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8d2720cb-fd26-0ed8-5e59-c9a062384966@gmail.com \
--to=adf.lists@gmail.com \
--cc=bcronce@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dendari92@gmail.com \
/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