Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Tim Higgins <tim@smallnetbuilder.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] REPOSTED: SmallNetBuilder Article: Does OFDMA really work? Part 2
Date: Thu, 28 May 2020 10:59:59 -0700	[thread overview]
Message-ID: <CAHb6LvqUrsX+xSc9D506RnZJf0MnmmbcgDXbTxr-OhhvPUcaNg@mail.gmail.com> (raw)
In-Reply-To: <79267524-8f69-cca5-f0de-99f30b630f5a@smallnetbuilder.com>

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

Iperf 2.0.14 supports write to read trip times for both TCP and UDP

https://youtu.be/LOGpXiAk_cc

Bob

On Thu, May 28, 2020 at 7:22 AM Tim Higgins <tim@smallnetbuilder.com> wrote:

> Hi Bob,
>
> Thanks for the suggestions. The iper2 suggests are for UDP, correct?
>
> As I said in the article, I'm done hunting this snark for now. Maybe
> others will take up the challenge.
> ===========
> Tim
> On 5/27/2020 1:16 PM, Bob McMahon wrote:
>
> I would make a small packet run too. For iperf2 use -l 40 and -b 20000pps
> and vary the pps number. I would hope that OFDMA would increase this.
>
> Also, don't forget about jitter - the derivative of latency. Some
> protocols care more about jitter than they do latency.
>
> I'd look into measuring the actual latency and jitter of the traffic vs
> using a ping as a proxy. This will be supported in iperf 2.0.14 using the
> write (server) side clock and --write-ack.  Better though is to synchronize
> the clocks and use one way trip times. While I like to synchronize the
> realtime clocks to the GPS atomic clock as the reference, using PTP and
> synchronizing to a common reference of any PC oscillator may be good
> enough. PTP stats will give you errors and corrections and per the
> corrections one can get an idea of the error.
>
> Thanks for posting. I really don't think OFDMA is going to affect such
> large latencies in a noticeable manner. I think it will be the ultra low
> latencies or near zero queuing that will matter.  For data center switches
> this is driven mostly by high frequency traders. For WiFi it's going to be
> newer games with VR/AR. Those latencies are going to need to be very low
> compared to today's use cases.
>
> my $0.02,
>
> Bob
>
> On Wed, May 27, 2020 at 7:37 AM Tim Higgins <tim@smallnetbuilder.com>
> wrote:
>
>> Tests have been redone and article is back up.
>> ===========================
>> Hi All,
>>
>> This article uses the benchmark test described in Part 1 to test 6 Wi-Fi
>> consumer routers. Results are not impressive.
>>
>> https://www.smallnetbuilder.com/wireless/wireless-features/33223-does-ofdma-really-work-part-2
>>
>> ===========
>> Tim
>> _______________________________________________
>> 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: 4455 bytes --]

      reply	other threads:[~2020-05-28 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 14:37 Tim Higgins
2020-05-27 17:16 ` Bob McMahon
2020-05-28 14:22   ` Tim Higgins
2020-05-28 17:59     ` Bob McMahon [this message]

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=CAHb6LvqUrsX+xSc9D506RnZJf0MnmmbcgDXbTxr-OhhvPUcaNg@mail.gmail.com \
    --to=bob.mcmahon@broadcom.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=tim@smallnetbuilder.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