From: Dave Taht <dave.taht@gmail.com>
To: Jan Ceuleers <jan.ceuleers@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Looking for a citation...
Date: Sun, 18 Aug 2024 08:47:02 -0700 [thread overview]
Message-ID: <CAA93jw68vSRSe_W7h6qgm63bmDfTgM+tcbBg5BQ1pYVdkrBPgg@mail.gmail.com> (raw)
In-Reply-To: <66c3c9fe-da65-443e-b188-c81adf13f73a@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2132 bytes --]
Actually I feel that at speeds greater than *50*Mbits, most of the bloat
moves to the wifi, but perhaps I should qualify it more, Modern wifi can do
almost 2gbits a few feet from the AP, but still has a dynamic range of
5Mbit to 2gbit. Interference, contention, range, all factor into when you
hit a FIFO "cliff", and stay there.
I wish I knew how many commercial APs outside of eero, cisco meraki,
gfiber, and starlink have adopted fq_codel. Certainly I am pleased as punch
at openwrt's adoption. And seeing at least a few fiber folk shipping better
wifi.
Moreso, if only more vendors did a RvRvlatency test like:
http://flent-newark.bufferbloat.net/~d/Airtime%20based%20queue%20limit%20for%20FQ_CoDel%20in%20wireless%20interface.pdf
A hugely mitigating factor is people self adapting to move closer to the AP
(or mesh), another is most traffic never cracks 20 mbit for very long.
I am sad that every coffee shop I frequent save one, has horrible
bufferbloat, but it usually only shows up when you try to do s
videoconference.
On Sun, Aug 18, 2024 at 8:32 AM Jan Ceuleers via Bloat <
bloat@lists.bufferbloat.net> wrote:
> On 18/08/2024 11:08, Rich Brown via Bloat wrote:
> > In various posts, I have baldly asserted that "above 300-500mbps ISP
> links, all the bufferbloat moves into the Wi-Fi."
> >
> > I am pretty sure that I someone on these lists stated that as fact.
> >
> > Could I get a link to a discussion that is definitive? Or a statement
> that is actually true that I can incorporate into my future posts? Many
> thanks.
>
> Quite evidently there are WiFi access points and clients available whose
> speeds exceed 500 Mbit/s, so in order to be able to make such a claim
> one would need to know the extent to which those newer WiFi technologies
> are not yet deployed.
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Artists/Musician Campout Aug 9-11
https://www.eventbrite.com/e/healing-arts-event-tickets-928910826287
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 3190 bytes --]
next prev parent reply other threads:[~2024-08-18 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 9:08 Rich Brown
2024-08-18 15:32 ` Jan Ceuleers
2024-08-18 15:47 ` Dave Taht [this message]
2024-08-18 16:01 ` David Lang
2024-08-18 16:12 ` Dave Taht
2024-08-18 18:43 ` dan
2024-08-18 18:48 ` [Bloat] [Make-wifi-fast] " Sebastian Moeller
2024-08-18 18:52 ` David Lang
2024-08-19 13:29 ` [Bloat] " Livingood, Jason
2024-08-19 22:12 ` [Bloat] [Make-wifi-fast] " Bob McMahon
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=CAA93jw68vSRSe_W7h6qgm63bmDfTgM+tcbBg5BQ1pYVdkrBPgg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jan.ceuleers@gmail.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