From: "Robert Chacón" <robert.chacon@jackrabbitwireless.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Herbert Wolverson <herberticus@gmail.com>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Integration system, aka fun with graph theory
Date: Sun, 30 Oct 2022 21:26:55 -0600 [thread overview]
Message-ID: <CAOZyJovHurVC=2GNGUc2jtMWqPFG_n39dMjkO5uF2uVP_Zf9+A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7RzeaQzMSgfsPytjVV9gubkZgQVLT2g78ZfF8Hv-foOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2067 bytes --]
> That's a lot to play with, so I'm taking my time. My gut likes the A/B
switch, currently.
Take your time, I'm just thrilled to see this working so well so far.
> I could feel the difference at my desk; fire up a video while a download
was running, and it simply "felt" like it responded better. TCP RTT times
are the best measure of "feel" I've found, so far.
I've experienced the same when our network switched from LibreQoS using
fq_codel to LibreQoS using CAKE. Really hard to quantify it but the
"snappiness" or "feel" is noticeable to end-users.
> We've tended to go with "median" latency as a guide, rather than mean.
Thanks to monitoring things beyond our control, some of the outliers tend
to be *really bad* - even if the network is fine. There's literally nothing
we can do about a customer trying to work with a malfunctioning system
somewhere (in space, for all I know!)
True. And it can be sort of helpful for troubleshooting WiFi latency issues
and bottlenecks inside the home and such.
> "monitor only" mode
Perhaps we can use ePPing just for this aspect? Or instead we could use
cpumap-pping but with all HTB classes set to high rates (no plan
enforcement) and no CAKE leafs.
> How about the idea of "metaverse-ready" metrics, with one table that is
preseem-like and another that's
Good idea. I've now added both a standard (preseem like) table and
"metaverse-ready" table of Node (AP) TCP Latency on the InfluxDB template.
On Sun, Oct 30, 2022 at 8:21 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> How about the idea of "metaverse-ready" metrics, with one table that is
> preseem-like and another that's
>
> blue = < 8ms
> green = < 20ms
> yellow = < 50ms
> orange = < 70ms
> red = > 70ms
>
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
--
Robert Chacón
CEO | JackRabbit Wireless LLC <http://jackrabbitwireless.com>
Dev | LibreQoS.io
[-- Attachment #2: Type: text/html, Size: 3217 bytes --]
next prev parent reply other threads:[~2022-10-31 3:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 21:33 Herbert Wolverson
2022-10-27 21:41 ` Dave Taht
2022-10-27 21:44 ` Dave Taht
2022-10-27 21:48 ` Robert Chacón
2022-10-28 0:27 ` dan
2022-10-28 12:40 ` Herbert Wolverson
2022-10-28 17:43 ` Herbert Wolverson
2022-10-28 19:05 ` Robert Chacón
2022-10-28 19:54 ` Herbert Wolverson
2022-10-28 21:15 ` Robert Chacón
2022-10-29 15:57 ` Herbert Wolverson
2022-10-29 19:05 ` Robert Chacón
2022-10-29 19:43 ` Dave Taht
2022-10-30 1:45 ` Herbert Wolverson
2022-10-31 0:15 ` Dave Taht
2022-10-31 1:15 ` Robert Chacón
2022-10-31 1:26 ` Herbert Wolverson
2022-10-31 1:36 ` Herbert Wolverson
2022-10-31 1:46 ` Herbert Wolverson
2022-10-31 2:21 ` Dave Taht
2022-10-31 3:26 ` Robert Chacón [this message]
2022-10-31 14:47 ` [LibreQoS] metaverse-ready metrics Dave Taht
2022-10-31 14:50 ` Dave Taht
2022-10-31 15:56 ` [LibreQoS] Integration system, aka fun with graph theory dan
2022-10-31 21:19 ` Herbert Wolverson
2022-10-31 21:54 ` Dave Taht
2022-10-31 21:57 ` Robert Chacón
2022-10-31 23:31 ` dan
2022-10-31 23:45 ` Dave Taht
2022-11-01 3:31 ` Dave Taht
2022-11-01 13:38 ` Herbert Wolverson
2022-10-29 19:18 ` Dave Taht
2022-10-30 1:10 ` Herbert Wolverson
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='CAOZyJovHurVC=2GNGUc2jtMWqPFG_n39dMjkO5uF2uVP_Zf9+A@mail.gmail.com' \
--to=robert.chacon@jackrabbitwireless.com \
--cc=dave.taht@gmail.com \
--cc=herberticus@gmail.com \
--cc=libreqos@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