General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Hal Murray <halmurray+mwf@sonic.net>
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	Starlink <starlink@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Cc: Hal Murray <halmurray+mwf@sonic.net>
Subject: Re: [Bloat] [Make-wifi-fast] [Starlink] bloat on wifi8 and 802.11 wg
Date: Sun, 01 Sep 2024 21:20:24 -0700	[thread overview]
Message-ID: <20240902042024.8A7E3620054@107-137-68-211.lightspeed.sntcca.sbcglobal.net> (raw)
In-Reply-To: Message from David Lang via Make-wifi-fast  <make-wifi-fast@lists.bufferbloat.net> of "Sun, 01 Sep 2024 19:59:43 -0700." <0p31n75o-9o83-o9q6-1315-2os9p65450s5@ynat.uz>


David Lang said:
> It really doesn't help that everyone in the industry is pushing for
> higher  bandwidth for a single host. That's a nice benchmark number, but
> not really  relevant int he real world.

> Even mu-mimo is of limited use as most routers only handle a handful of
> clients.

> But the biggest problem is just the push to use wider channels and gain
> efficiency in long-running bulk transfers by bundling lots of IP packets
> into a  single transmission. This works well when you don't have
> congestion and have a  small number of clients. But when you have lots of
> clients, spanning many  generations of wifi technology, you need to go to
> narrower channels, but more  separate routers to maximize the fairness of
> available airtime. 

What does that say about the minimal collection of gear required in a test 
lab?

If you had a lab with plenty of gear, what tests would you run?

How many different tests would it take to give reasonable coverage?


-- 
These are my opinions.  I hate spam.




  reply	other threads:[~2024-09-02  4:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 15:28 [Bloat] WiFi Livingood, Jason
2024-05-08 15:35 ` [Bloat] bloat on wifi8 and 802.11 wg Dave Taht
2024-05-08 21:18   ` Dorothy Stanley
2024-05-08 21:22   ` Dorothy Stanley
2024-09-02  1:15   ` [Bloat] [Make-wifi-fast] " Bob McMahon
2024-09-02  2:59     ` [Bloat] [Starlink] " David Lang
2024-09-02  4:20       ` Hal Murray [this message]
2024-09-02  5:05         ` [Bloat] [Make-wifi-fast] [Starlink] " David Lang
2024-09-02 15:04           ` [Bloat] Real-world testing: " Rich Brown
2024-09-02 15:09             ` [Bloat] [Make-wifi-fast] " Sebastian Moeller
2024-09-02 15:37               ` David Lang
2024-09-02 17:28           ` [Bloat] [Make-wifi-fast] [Starlink] bloat on " Bob McMahon
2024-09-02 17:31             ` Frantisek Borsik
2024-09-02 18:02             ` Bob McMahon
2024-09-03  3:20             ` David Lang
2024-09-03 15:42               ` Bob McMahon
2024-09-02 23:22         ` David Collier-Brown
2024-09-02 12:09       ` [Bloat] [Starlink] [Make-wifi-fast] " Michael Richardson
2024-09-02 16:37       ` Brandon Butterworth

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=20240902042024.8A7E3620054@107-137-68-211.lightspeed.sntcca.sbcglobal.net \
    --to=halmurray+mwf@sonic.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=starlink@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