Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Rich Brown <richb.hanover@gmail.com>
Cc: rjmcmahon via Make-wifi-fast
	<make-wifi-fast@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Looking for a citation...
Date: Sun, 18 Aug 2024 20:48:41 +0200	[thread overview]
Message-ID: <8D08AFCD-B80E-46B3-B18F-B0864E8095F3@gmx.de> (raw)
In-Reply-To: <93639364-6937-4EE6-B218-2A02AF212362@gmail.com>

Hi Rich,


> On 18. Aug 2024, at 11:08, Rich Brown via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net> 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.

[SM] This is somewhat hard to assess, as most WiFi gear likely lives in home networks (and is not replaced routinely*) and does not give any upstream feedback about which MCS and number of streams are typically achievable. Operators of  managed WIFi networks should know, but I guess for those this is pretty intimate information that they might not want to share with the competitors.

But a rule of thumb is that achievable throughput for WiFi is closer to 50% of the MCS table rate (see https://mcsindex.com/), I would guess that the bulk of existing stations will have >= 3 antennas and will be pre-802.11.ax, but that still leaves guessing the channel width... but if we assume 80 MHz channels (anecdotally based on looking around in my WiFi surround) the highest likely MCS rate would be 1170, which gets us to the upper end of you estimate once we account for the 50% utilisation factor... But given the amount of assumptions we had to make, I am not sure that offers the certainty you are after...

*) I expect wildly different update schedules for routers/APs, notebooks, and mobile devices. Smartphones might on the forefront with some folks replacing them every 24 months, and laptops/APs on much slower schedules.... so even if WiFi6/7 gear starts hitting some customer premises, I expect a looooong tail of WiFi4/5 devices


> 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.
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast



  reply	other threads:[~2024-08-18 18:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18  9:08 Rich Brown
2024-08-18 18:48 ` Sebastian Moeller [this message]
2024-08-18 18:52   ` [Make-wifi-fast] [Bloat] " David Lang
2024-08-19 13:29 ` Livingood, Jason
2024-08-19 22:12   ` 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/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8D08AFCD-B80E-46B3-B18F-B0864E8095F3@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=richb.hanover@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