From: Jonathan Morton <chromatix99@gmail.com>
To: Matt Mathis <mattmathis@google.com>
Cc: David Collier-Brown <davecb@spamcop.net>,
Ken Rice <krice@freeswitch.org>,
bloat <bloat@lists.bufferbloat.net>,
Anthony Minessale II <anthm@freeswitch.com>
Subject: Re: [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE?
Date: Tue, 8 Sep 2020 20:09:42 +0300 [thread overview]
Message-ID: <0FD03007-9D6F-4110-858D-0A75834DA580@gmail.com> (raw)
In-Reply-To: <CAH56bmCH6nHyAQrjmOt71YRwm0GB8QRgMir77AHa421GO72HEg@mail.gmail.com>
> On 8 Sep, 2020, at 7:48 pm, Matt Mathis via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> To be simplistic, you might just talk about cake vs (bloated) drop tail. To be thorough, you also need to make the case that cake is better than other AQMs. This feels like too much for LWN, but silence on other solutions might trigger skeptics.
Personally, my position is:
1: Bloated dumb FIFOs are terrible.
2: Basic AQM is good. This can be as simple as TBF+WRED; it solves a large part of the basic problem by eliminating multi-second queue delays. In some cases this can solve very serious problems, such as DNS lookups failing when the link is loaded, quite adequately. Properly configured, you can keep queue delays below the 100ms threshold for reasonable VoIP performance.
3: FQ-AQM is better. That generally means HTB+fq_codel, but other forms of this exist. It means essentially zero added delay for non-saturating flows. It's an easy way to make DNS, VoIP and online gaming work nicely without having to restrict data-hungry applications.
4: Cake offers some extra tools and aims to be easier (more intuitive) to configure. Currently, it is the best solution for slow and medium-speed broadband (up to 100Mbps), and can also be used at higher speeds with some care, mostly regarding device performance.
- Jonathan Morton
next prev parent reply other threads:[~2020-09-08 17:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 18:27 David Collier-Brown
2020-08-09 19:18 ` Tom Henderson
2020-08-09 21:35 ` Jonathan Morton
2020-08-10 12:57 ` David Collier-Brown
2020-08-10 14:00 ` Daniel Sterling
2020-08-10 15:08 ` Tom Henderson
2020-08-10 15:34 ` Sebastian Moeller
2020-08-10 15:57 ` Jonathan Morton
2020-08-10 16:04 ` Tom Henderson
2020-08-11 12:43 ` Daniel Sterling
2020-08-11 13:57 ` Kenneth Porter
[not found] ` <D8B6D86243E4539BBA58E32C@172.27.17.193>
2020-08-11 14:09 ` Daniel Sterling
2020-08-11 14:11 ` Daniel Sterling
2020-08-11 16:19 ` Kenneth Porter
2020-08-10 17:58 ` Jonathan Foulkes
2020-08-10 19:13 ` Carlos R. Pasqualini
2020-08-10 20:28 ` Dave Collier-Brown
2020-08-11 12:41 ` Michael Yartys
2020-08-10 14:16 ` [Bloat] Sidebar to "How about a topical LWN article on demonstrating the real-world goodness of CAKE?" David Collier-Brown
2020-08-11 15:48 ` [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE? Simon Barber
2020-09-05 18:52 ` Dave Taht
2020-09-05 20:35 ` Dave Collier-Brown
2020-09-07 9:23 ` Toke Høiland-Jørgensen
2020-09-07 11:33 ` Dave Collier-Brown
2020-09-07 17:20 ` David Collier-Brown
2020-09-08 15:43 ` Dave Taht
2020-09-08 16:48 ` Matt Mathis
2020-09-08 17:09 ` Jonathan Morton [this message]
2020-09-10 15:08 ` Anthony Minessale II
2020-09-10 16:52 ` Dave Collier-Brown
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=0FD03007-9D6F-4110-858D-0A75834DA580@gmail.com \
--to=chromatix99@gmail.com \
--cc=anthm@freeswitch.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.net \
--cc=krice@freeswitch.org \
--cc=mattmathis@google.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