From: Dave Taht <dave.taht@gmail.com>
To: "Robert Chacón" <robert.chacon@jackrabbitwireless.com>
Cc: Herbert Wolverson <herberticus@gmail.com>,
libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] ookla speedtest results?
Date: Mon, 24 Oct 2022 13:31:32 -0700 [thread overview]
Message-ID: <CAA93jw4q2_fyc78VCLL3yk1_AV3b8hvRrpR2pysaiXs2TbpLCw@mail.gmail.com> (raw)
In-Reply-To: <CAOZyJos46g9n6_eSbr9ha8jt7afGJWeW+uxAgGUmhPveg1q-_g@mail.gmail.com>
On Mon, Oct 24, 2022 at 1:17 PM Robert Chacón
<robert.chacon@jackrabbitwireless.com> wrote:
>
> Here's a customer on a 200/30 Mbps plan via Fixed Wireless.
> LibreQoS using cake diffserv4.
> LTU-LR is the client radio. Home WiFi is 802.11AC which is where most of the bloat comes from.
Yep! I'd like to collect a list of APs that are decent here, out of
the box. 40ms does not seem "bad".
It would be pretty cool to be able to A/B test one of these:
https://openwrt.org/toh/tp-link/eap615-wall
with stock vs openwrt vs my current openwrt branch, on a test like
this. I don't know enough about the
structure of speedtest and wifi is naturally jittery, but I was down
to 8ms induced latency on a variety of tests
on the mt76 chipset(s) before I put it down. (more important for wifi,
is multi-station loading)
Anyone fiddling with openwisp.org?
> When he tests by Ethernet bloat is 8ms instead of 40ms.
thanks very much! That's gorgeous!
https://www.speedtest.net/result/13846818812
I keep hoping speedtest are internally dissecting data from certain AS
numbers and going "woah!" WTF are they doing?
>
> On Mon, Oct 24, 2022 at 12:28 PM Dave Taht via LibreQoS <libreqos@lists.bufferbloat.net> wrote:
>>
>> Although I'm enjoying a good wide-ranging debate... is it possible one
>> or more of you could
>> take a speedtest.net test, click on results so you see the
>> "responsiveness" data, and post a screen shot?
>>
>> Perlease??
>> _______________________________________________
>> LibreQoS mailing list
>> LibreQoS@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/libreqos
>
>
>
> --
> Robert Chacón
> CEO | JackRabbit Wireless LLC
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2022-10-24 20:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 13:51 Dave Taht
2022-10-24 14:01 ` Herbert Wolverson
2022-10-24 15:02 ` Robert Chacón
2022-10-24 15:09 ` Dave Taht
2022-10-24 15:20 ` dan
2022-10-24 15:27 ` Dave Taht
2022-10-24 15:31 ` dan
2022-10-24 16:30 ` Herbert Wolverson
2022-10-24 16:48 ` dan
2022-10-24 17:14 ` Dave Taht
2022-10-24 17:30 ` dan
2022-10-24 17:39 ` Dave Taht
2022-10-24 17:34 ` Robert Chacón
2022-10-24 17:41 ` Herbert Wolverson
2022-10-24 17:42 ` Dave Taht
2022-10-24 17:46 ` dan
2022-10-24 17:57 ` Dave Taht
2022-10-24 18:03 ` dan
2022-10-24 18:06 ` Herbert Wolverson
2022-10-24 18:22 ` Dave Taht
2022-10-24 18:27 ` Dave Taht
2022-10-24 20:16 ` Robert Chacón
2022-10-24 20:31 ` Dave Taht [this message]
2022-10-24 20:49 ` Mark Steckel
2022-10-24 18:14 ` Dave Taht
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4q2_fyc78VCLL3yk1_AV3b8hvRrpR2pysaiXs2TbpLCw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=herberticus@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=robert.chacon@jackrabbitwireless.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