From: Dave Taht <dave.taht@gmail.com>
To: George Amanakis <gamanakis@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Cake] inbound cake or fq_codel shaping fails on cable on netflix reno
Date: Sat, 21 Jul 2018 10:42:43 -0700 [thread overview]
Message-ID: <CAA93jw4ru9dJm16_fGwaASHo0wP63ps77VbvD35bD3QCiZgaBg@mail.gmail.com> (raw)
In-Reply-To: <edd57b2ab33732ad1b7266f69d172c47017d285a.camel@gmail.com>
On Sat, Jul 21, 2018 at 10:28 AM Georgios Amanakis <gamanakis@gmail.com> wrote:
>
> The previous one was with:
> net.ipv4.tcp_congestion_control=cubic
>
> I retried with:
> net.ipv4.tcp_congestion_control=reno
>
> Georgios
In the fast test this has no effect on the remote server's tcp, it's
always going to be reno.
Trying to cross-check behavior using our tests...
There isn't a specific reno setting test in flent for tcp_download as
best as I recall, so I was just calling netperf -H wherever -l 60 --
-K reno,reno
then running the flent ping test as previous mentioned.
(flent-fremont.bufferbloat.net and flent-newark both support reno bbr
and cubic, I haven't checked the others)
PS A side note is that we are not fully successfully moving the
inbound bottleneck to cake (at least in the cable case), as we do get
quite a bit of queuing delay even with linux tcp driving the tests.
I'd long written this off as inevitable, due to the bursty cable mac
but I'm grumpy this morning. 0 delay via fq would be better than even
the 15-40ms I'm getting now with linux flows.....
reno bbr cubic
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-07-21 17:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 16:09 [Cerowrt-devel] " Dave Taht
2018-07-21 17:20 ` [Cerowrt-devel] [Cake] " Georgios Amanakis
2018-07-21 17:23 ` Jonathan Morton
2018-07-21 17:44 ` Georgios Amanakis
2018-07-21 17:47 ` Dave Taht
2018-07-21 18:18 ` Georgios Amanakis
2018-07-21 18:20 ` Dave Taht
2018-07-21 18:23 ` Georgios Amanakis
2018-07-21 20:01 ` Dave Taht
2018-07-21 20:24 ` Jonathan Morton
2018-07-21 20:36 ` Dave Taht
2018-07-21 17:24 ` Arie
2018-07-21 17:27 ` Dave Taht
2018-07-21 17:28 ` Georgios Amanakis
2018-07-21 17:42 ` Dave Taht [this message]
2018-07-21 19:57 ` Toke Høiland-Jørgensen
2018-07-24 2:36 ` Dave Taht
2018-07-24 4:17 ` Georgios Amanakis
2018-07-22 9:57 ` Pete Heist
2018-07-22 10:29 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4ru9dJm16_fGwaASHo0wP63ps77VbvD35bD3QCiZgaBg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=gamanakis@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