From: Benjamin Cronce <bcronce@gmail.com>
To: "Jonas Mårtensson" <martensson.jonas@gmail.com>
Cc: pete@heistp.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] powerboost and sqm
Date: Wed, 4 Jul 2018 15:25:27 -0500 [thread overview]
Message-ID: <CAJ_ENFFA4qiV+sf+uJUek3zt+3bub=4cMfdYaOuqjJ3yxi9_aw@mail.gmail.com> (raw)
In-Reply-To: <CAM9iV=L0JkFfGRV3_NqE7C14korSzD-RegSe2aZ1MCuRYYtUrg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2691 bytes --]
Strict token bucket without fair queuing can cause packetloss bursts for
all flows. In my personal experience when dealing with a low(single digit)
RTT, I would find that my ex-50Mb connection would accept a 1Gb burst and
ACK all of the data. Then the sender would think I had a 1Gb link and keep
sending at 1Gb. Around the 200ms mark, there would be a steep slope where
all of my traffic would suddenly see ~5% loss for the rest of that second.
Once steady state was reached, it was fine. The issue seemed to have a
baseline relative to the ratio between the provisioned rate and the burst
rate, with a dynamic multiplier not-quite-linearly driven by the link's
current utilization. At ~0% average utilization, bursts that lasted longer
than the bucket could induce maximum, and not much of an issue past 80%.
I could reliably recreate the issue by loading a high bandwidth video on
youtube and jumping around the timeline to unbuffered segments. I had
anywhere from 6ms to 12ms latency to youtube CDNs depending on the route
and which datacenter. Not only could I measure the issue with icmp at 100
samples per second, but I could reliably see issues in-game with either UDP
or TCP based games. Simply shaping to 1-2Mb below my provisioned rate and
enabling Codel seemed to alleviate the issue into not-noticing.
On Sun, Jul 1, 2018 at 4:50 PM Jonas Mårtensson <martensson.jonas@gmail.com>
wrote:
>
>
> On Sat, Jun 30, 2018 at 9:46 AM Pete Heist <pete@heistp.net> wrote:
>
>>
>> On Jun 30, 2018, at 8:26 AM, Jonas Mårtensson <martensson.jonas@gmail.com>
>> wrote:
>>
>>>
>>> I played around with flent a bit, here are some example plots:
>>
>> https://dl.dropbox.com/s/facariwkp5x5dh1/flent.zip?dl=1
>>
>> The short spikes are not seen with flent so I'm led to believe these are
>> just a result of running the "Hi-Res" dslreports test in a browser. In the
>> flent rrul test, up to about 10 ms induced latency can be seen during the
>> "powerboost" phase but after that it is almost zero. I'm curious about how
>> this is implemented on the ISP side. If anything, sqm seems to induce a bit
>> more latency during the "steady-state" phase.
>>
>>
>> You may also want to try running flent with --socket-stats and making a
>> tcp_rtt plot. You should see a significant difference in TCP RTT between
>> sfq and anything that uses CoDel.
>>
>
> In case anyone is curious I tried this and the tcp rtt plot looks very
> similar to the ping rtt plot, i.e. the latencies are the same.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 4600 bytes --]
next prev parent reply other threads:[~2018-07-04 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 10:56 Jonas Mårtensson
2018-06-29 11:23 ` Sebastian Moeller
2018-06-30 6:26 ` Jonas Mårtensson
2018-06-30 7:20 ` Jonathan Morton
2018-06-30 7:46 ` Pete Heist
2018-06-30 11:22 ` Dave Taht
2018-07-01 21:49 ` Jonas Mårtensson
2018-07-04 20:25 ` Benjamin Cronce [this message]
2018-06-29 12:22 ` Jonathan Morton
2018-06-29 14:00 ` Dave Taht
2018-06-29 14:42 ` Sebastian Moeller
2018-06-29 15:45 ` Jonas Mårtensson
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ_ENFFA4qiV+sf+uJUek3zt+3bub=4cMfdYaOuqjJ3yxi9_aw@mail.gmail.com' \
--to=bcronce@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=martensson.jonas@gmail.com \
--cc=pete@heistp.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