From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Rpm] [Make-wifi-fast] openwrt: some messy rpm vs ookla vs waveform vs rrul tests
Date: Mon, 11 Jul 2022 15:27:15 -0700 [thread overview]
Message-ID: <CAHb6LvoqqUmsLU9MJwTTwHY18qrENchi6kqHtm23z7s8S2cuwA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4=72xN+fnRr0WW2_z44-tC0KZR5naofwM1NUTvjfzzsA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2440 bytes --]
The WiFi testing matrix is huge. My only help is to publish iperf 2 and
pyflows as open source <https://sourceforge.net/projects/iperf2/>. There
are ways to build test rigs using programmable attenuators and variable
phase shifters, splitters, combiners etc. Then use statistical process
controls (SPC) to automate monitoring for anomalies and regressions. It's a
lot of sw work and each test rig costs a lot of money. I find this level of
testing is typically beyond to scope of "free and voluntary labor."
I'd agree that there are likely many poorly behaving devices.
Bob
On Mon, Jul 11, 2022 at 11:52 AM Dave Taht via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:
> the test matrix for wifi is mindboggling. We've been battling a string
> of regressions in the present openwrt release candidate,
> for months now, and finally got past the crash bugs a week or two back.
>
> https://forum.openwrt.org/t/aql-and-the-ath10k-is-lovely/59002/680
>
> One regression of note is seeing a rpm score of 3600 on the old
> release and only 800 now.
>
> I am convinced that 99.99999% of the world's consumer APs and clients
> are behaving this badly, in the first place.
>
> If anyone else would like to help, or has resources to throw in to
> test this upcoming release, it would be appreciated!
>
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #1.2: Type: text/html, Size: 3253 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
prev parent reply other threads:[~2022-07-11 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 18:52 [Rpm] " Dave Taht
2022-07-11 22:27 ` 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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHb6LvoqqUmsLU9MJwTTwHY18qrENchi6kqHtm23z7s8S2cuwA@mail.gmail.com \
--to=bob.mcmahon@broadcom.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=rpm@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