General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Tom Henderson <tomh@tomh.org>
To: davecb@spamcop.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE?
Date: Sun, 9 Aug 2020 12:18:20 -0700	[thread overview]
Message-ID: <225a9c89-ac76-f21e-1450-5deeb3cd23eb@tomh.org> (raw)
In-Reply-To: <a21f6b6f-7bf4-ed30-8b11-8f733487b37b@rogers.com>

On 8/9/20 11:27 AM, David Collier-Brown wrote:
>  I suspect not enough people are aware of the later efforts of the 
> bufferbloat team, so I'm thinking of one or two articles, starting 
> with LWN and an audience of aficionados.
>
> The core community is aware of what we've done, but in my view we 
> haven't converted "grandma". Grandma, as well as a whole bunch of 
> ordinary engineers and partners of engineers, are dependent on 
> debloated performance because they're working at home now, and 
> competing with granddaughter playing video games while they're trying 
> to hold a video call.
>
> Right now, my colleagues at work suffer from more than a second of 
> bloat-related lag. They therefore tend to speak over each other on 
> con-calls, apologize, start again and talk over each other, again. 
> After a little while, the picture becomes a distinctly silly one: a 
> bunch of grown adults putting their hands up and waving, like little 
> kids in school. No-one has called out “me, me, teacher” yet, but I 
> expect it any time.
>
> I propose we show the results in terms that we can explain to Grandma, 
> specifically concentrating on functioning VOIP. I just upgraded to 
> Fedora 31, and the networking is absolutely stock, so I make a perfect 
> victim/guinea-pig (;-))
>
> Who's interested?

Are the risks and tradeoffs well enough understood (and visible enough 
for troubleshooting) to recommend broader deployment?

I recently gave openwrt a try on some hardware that I ultimately 
concluded was insufficient for the job.  Fairly soon after changing out 
my access point, I started getting complaints of Wi-Fi dropping in my 
household, especially when someone was trying to videoconference.  I 
discovered that my AP was spontaneously rebooting, and the box was 
getting hot.

I am also wondering about what features will be lost if/when the device 
is flashed from the commercial firmware.  Does openwrt have access to 
all of the available Wi-Fi 11ac rates, and how does rate control 
compare?  The commercial devices offer proprietary media/device 
prioritization settings; does CAKE/SQM outperform them?  Many commercial 
APs or mesh systems have smartphone apps with features like parental 
controls; that kind of control will be lost.  What about 11ax support?

- Tom



  reply	other threads:[~2020-08-09 19:18 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 [this message]
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
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=225a9c89-ac76-f21e-1450-5deeb3cd23eb@tomh.org \
    --to=tomh@tomh.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.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