From: Erkki Lintunen <erkki.lintunen@iki.fi>
To: Tim Higgins <tim@smallnetbuilder.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Flent traffic direction convention
Date: Tue, 31 Mar 2020 16:48:49 +0300 [thread overview]
Message-ID: <6160f18c-948c-65f2-41d1-82c35136835d@iki.fi> (raw)
In-Reply-To: <1697eb13-068d-f518-35d6-1d1495feab40@smallnetbuilder.com>
On 3/26/20 11:22 PM, Tim Higgins wrote:
> Second question: Is there any documentation that can help me figure out
> exactly what traffic is running in each test type?
Not exactly an answer to the question.
I found following pages very helpful when three years ago I challenged
myself with Flent to measure WiFi network performance and max it out
with network devices I had at hand at the time.
(One ap blew up it's two capasitors. Visually and operationally the ap
was working as normal but measurements showed drastic drop in
performance. Light odor and inspection of el-capasitor burned tops did
confirm the hard to believe experience.)
<https://www.bufferbloat.net/projects/bloat/wiki/RRUL_Chart_Explanation/>
The above page provides link to this page.
<https://burntchrome.blogspot.com/2016/12/cake-latest-in-sqm-qos-schedulers.html>
Experience showed up Flent's feature to compare data sets very educating
and powerfull, not only with the box-plot chart as the pages show. Took
time to get mentaly bend to read and interpret the Flent charts instead
of only numbers I was used to with iperf and other tools.
In my quest I did a change, measured it, compared to the previous set
and reviewed, if the change showed any measurable effect. Finally I
compared the sets of the very first and the last. I was totally driven
by measurements on my way myth busting many my beliefs for a performant
network.
The quest changed my definition for "getting max out of a network". Now
the max is all quantities in effect at any time: fairness, lowest
possible latency and highest possible bitrate. Looking at many published
benchmarks today, I still think, max seams to mean just a maximum
bitrate and other qualities are _supposed_ to derive from it.
Hope this is for any help.
- Erkki
next prev parent reply other threads:[~2020-03-31 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 21:22 Tim Higgins
2020-03-27 11:05 ` Toke Høiland-Jørgensen
2020-03-27 11:31 ` Tim Higgins
2020-03-27 12:28 ` [Make-wifi-fast] [Flent-users] " Toke Høiland-Jørgensen
2020-03-31 13:48 ` Erkki Lintunen [this message]
2020-03-31 13:59 ` [Make-wifi-fast] " Tim Higgins
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=6160f18c-948c-65f2-41d1-82c35136835d@iki.fi \
--to=erkki.lintunen@iki.fi \
--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