From: Rich Brown <richb.hanover@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Slowly ... slowly ... the word is getting out...
Date: Fri, 27 Aug 2021 10:25:03 -0400 [thread overview]
Message-ID: <A852C98D-6D1B-4A7B-9DA7-1E07CA5ADBC6@gmail.com> (raw)
Yet another anecdote: Google Alerts for "bufferbloat" showed me this: https://www.reddit.com/r/Xiaomi/comments/pb7jpc/bufferbloat_latency_while_streaming_on_mi_aiot/
> > ... Currently, I am using the Mi R3 (very old) and while it is better than my ISP's one that doesn't even have QoS, it's not amazing like fq_codel or cake...
> ... Short answer: no, not even close to fq-codel, and qos is mostly garbage...
Five (or maybe even two) years ago, the comments would have been virulently pro-QoS, impugning your manhood for not getting it set up properly for whatever combination of games, apps, etc. you were running.
Now people on Reddit are actively talking about SQM as the right solution to the problem. Maybe the tide is turning.
Rich
PS That doesn't mean that we should stop blowing our own horn on this, trying to spread the word more broadly...
reply other threads:[~2021-08-27 14:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=A852C98D-6D1B-4A7B-9DA7-1E07CA5ADBC6@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.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