From: Jonathan Morton <chromatix99@gmail.com>
To: moeller0@gmx.de
Cc: tomh@tomh.org, sterling.daniel@gmail.com, davecb@spamcop.net,
dave.collier-brown@indexexchange.com,
bloat@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE?
Date: Mon, 10 Aug 2020 15:57:41 +0000 [thread overview]
Message-ID: <n5xm4z.qeuv08.2wxsbn-qmf@smtp.gmail.com> (raw)
In-Reply-To: <87878C8E-88D6-4218-A3D9-1CAE99CB1B59@gmx.de>
> The current best practice seems to be to instantiate cake/SQM on a reasonably fixed rate wan link and select WiFi cards/socs that offer decent airtime fairness.
> Works pretty well in practice...
Yes, AQL does essentially the right thing here, again along the lines of limiting the influence of one machine's load on another's performance, and completely automatically since it has faurly direct information and control over the relevant hardware. Cake is designed to deal with wired links where the capacity doesn't change much, but the true bottleneck is typically not at the device exerting control.
On that note, there is a common wrinkle whereby the bottleneck may shift between the private last mile link and some shared backhaul in the ISP at different times of day and/or days of week. Locally I've seen it vary between 20M (small hours, weekday) and 1Mbps (weekend evening). When Cake is configured for one case but the situation is different, the results are obviously suboptimal. I'm actually now trying a different ISP to see if they do better in the evenings.
Evenroute's product includes automatic detection of and scheduling for this case, assuming that it follows a consistent pattern over a weekly period. Once set up, it is essentially a cronjob adjusting Cake's parameters dynamically, so providing a manual setup for the general OpenWRT community should be feasible. On “tc qdisc change”, Cake usually doesn't drop any packets, so parameters can be changed frequently if you have a reason for it.
next prev parent reply other threads:[~2020-08-10 15:57 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 [this message]
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
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=n5xm4z.qeuv08.2wxsbn-qmf@smtp.gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.collier-brown@indexexchange.com \
--cc=davecb@spamcop.net \
--cc=moeller0@gmx.de \
--cc=sterling.daniel@gmail.com \
--cc=tomh@tomh.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox