Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Status of the industry on over buffering at the WiFi air interface
Date: Wed, 12 Feb 2020 16:36:44 -0800	[thread overview]
Message-ID: <CAHb6Lvp5MhtD6QYvmsLstw5waCoROXq1z=Zj4YFPBGStsfxE0g@mail.gmail.com> (raw)
In-Reply-To: <1581552513.586428831@apps.rackspace.com>

[-- Attachment #1: Type: text/plain, Size: 2775 bytes --]

hmm, not sure if this helps but "excess queueing" can be hard to define.

Do you know the operating systems for the WiFi devices and if tooling can
be loaded upon them?  iperf clients samples RTT and CWND for linux
machines. Iperf 2.0.14 (in development) has a lot of latency related
features

Also, if there is control over the AIFS one can set that for the high rates
devices such that they always win and the lower rate ones always lose.  If
that solves things it does suggest WiFi tx queues developing per the TXOP
arbitration and air transmission as an issue.  Standard cwmin/cwmax isn't
as effective though it won't allow high rates to starve low rates devices
as AIFS might (depending upon the values)

I use latency to measure the performance and define bounds that way and
it's very specific to use cases.  IT does require clock sync. My devices
have GPS disciplined oscillators which aren't common.

As an aside, the HULL approach of phantom queues looks interesting.
https://people.csail.mit.edu/alizadeh/papers/hull-nsdi12.pdf

Bob

On Wed, Feb 12, 2020 at 4:08 PM David P. Reed <dpreed@deepplum.com> wrote:

> A friend of mine (not a network expert, but a gadget freak), has been
> deploying wireless security cameras at his home and vacation home. He uses
> a single WiFi AP in each place, serving the security cameras etc.
>
> What he observes is this:
>
> Whenever anyone on a laptop in one of the homes uploads a modest sized
> file (over the same WiFi) the security systems all lose data.
>
> Now I can't go to his home to diagnose this, but I've asked him to check
> out his cable bufferbloat using dslreports, and he gets no bufferbloat
> there. But it sure looks like *severe* lag under load is affecting the
> security camera feed to the cloud servers that the company that sells the
> security cameras provides.
>
> So, is there a way to simply *diagnose* the WiFi air link for excess
> queueing in all the high rate WiFi devices? Something a non-net-head could
> do?
>
> The situation around congestion control in the industry continues to
> royally suck, in my opinion. The vendors don't care, the ISPs don't care
> (they can sell a higher speed connection than is actually needed and
> super-fabulous MIMO gadgets that still don't quite solve the problem).
>
> I'm an old guy, basically retired. I'm sad because the young folks remain
> clueless.
>
> And it's been decades since bufferbloat was discuvered, and the basic
> issue of congestion signalling being needed. I'm sure 5G (whatever it
> really is) is not paying attention to this network level congestion issue...
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast

[-- Attachment #2: Type: text/html, Size: 3446 bytes --]

  reply	other threads:[~2020-02-13  0:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13  0:08 David P. Reed
2020-02-13  0:36 ` Bob McMahon [this message]
2020-02-13  1:56   ` David P. Reed
2020-02-13  6:27     ` Bob McMahon
     [not found]     ` <mailman.471.1581575247.1241.make-wifi-fast@lists.bufferbloat.net>
2020-02-13 21:32       ` Bob McMahon
2020-02-13 22:23         ` David P. Reed
2020-02-13 22:36           ` Jonathan Morton
2020-02-13 23:49             ` Bob McMahon
2020-02-14 16:40             ` David P. Reed

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='CAHb6Lvp5MhtD6QYvmsLstw5waCoROXq1z=Zj4YFPBGStsfxE0g@mail.gmail.com' \
    --to=bob.mcmahon@broadcom.com \
    --cc=dpreed@deepplum.com \
    --cc=make-wifi-fast@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