From: "Robert Chacón" <robert.chacon@jackrabbitwireless.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Before/After Performance Comparison (Monitoring Mode)
Date: Sat, 5 Nov 2022 10:44:47 -0600 [thread overview]
Message-ID: <CAOZyJotBGXRdiL0xWOi4o-U+YKershOgFmmKvSeDWohGQ3njHQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
I was hoping to add a monitoring mode which could be used before "turning
on" LibreQoS, ideally before v1.3 release. This way operators can really
see what impact it's having on end-user and network latency.
The simplest solution I can think of is to implement Monitoring Mode using
cpumap-pping as we already do - with plain HTB and leaf classes with no
CAKE qdisc applied, and with HTB and leaf class rates set to impossibly
high amounts (no plan enforcement). This would allow for before/after
comparisons of Nodes (Access Points). My only concern with this approach is
that HTB, even with rates set impossibly high, may not be truly
transparent. It would be pretty easy to implement though.
Alternatively we could use ePPing
<https://github.com/xdp-project/bpf-examples/tree/master/pping> but I worry
about throughput and the possibility of latency tracking being slightly
different from cpumap-pping, which could limit the utility of a comparison.
We'd have to match IPs in a way that's a bit more involved here.
Thoughts?
[-- Attachment #2: Type: text/html, Size: 1197 bytes --]
next reply other threads:[~2022-11-05 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 16:44 Robert Chacón [this message]
2022-11-08 14:23 ` Toke Høiland-Jørgensen
2022-11-08 15:44 ` Robert Chacón
2022-11-08 16:04 ` Herbert Wolverson
2022-11-08 16:02 ` Herbert Wolverson
2022-11-08 18:53 ` Simon Sundberg
2022-11-10 22:10 ` Dave Taht
2022-11-11 14:23 ` 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=CAOZyJotBGXRdiL0xWOi4o-U+YKershOgFmmKvSeDWohGQ3njHQ@mail.gmail.com \
--to=robert.chacon@jackrabbitwireless.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