From: Rich Brown <richb.hanover@gmail.com>
To: Rich Brown via Bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Re: SQM becoming mainstream (finally)
Date: Sat, 13 Jun 2026 13:09:57 -0400 [thread overview]
Message-ID: <5A195D2C-C9B8-49B9-9AEC-410A2E1C9018@gmail.com> (raw)
In-Reply-To: <67CC0F9C-0228-4A70-87C2-13C0E5E5FA32@gmail.com>
Another one - with a heading of "More bandwidth won't fix a queue problem - the fix is a smarter queue”... (make sure your ad blocker is turned on)
https://www.makeuseof.com/diagnosed-wi-fi-problems-with-free-test-that-speed-tests-cant-show/
There's a free test that reveals exactly why your internet feels slow — even when the speed test says it's fine
makeuseof.com
> On Jun 12, 2026, at 08:49, Rich Brown <richb.hanover@gmail.com> wrote:
>
> I regularly receive email alerts from alerts.google.com for “bufferbloat” and “high ping time”. My inbox receives daily notes with links to Reddit articles asking, “could this really be bufferbloat?”, and occasional announcements of “the BEST gaming router of 2025/2026/2027...”
>
> I saw an interesting review today [1]: I don’t put any particular credence in their rankings of the various routers, but I found it delightful that this was the first point in the entire article:
>
> * Ping spikes during gaming are usually caused by home network congestion, not ISP speed, and a gaming router with quality of service (QoS) or SQM directly fixes that
>
> Dave would be so pleased that Bufferbloat and SQM are finally entering mainstream consciousness.
>
> [1] https://www.analyticsinsight.net/gaming/best-gaming-routers-in-2026-for-low-latency-and-high-speed-performance
next prev parent reply other threads:[~2026-06-13 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 12:49 [Bloat] SQM becoming mainstream (finally) Rich Brown
2026-06-13 17:09 ` Rich Brown [this message]
2026-06-13 17:44 ` [Bloat] " 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/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=5A195D2C-C9B8-49B9-9AEC-410A2E1C9018@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