From: Dave Taht <dave.taht@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: [Make-wifi-fast] graphing airtime fairness in wifi
Date: Mon, 18 Apr 2016 15:35:10 -0700 [thread overview]
Message-ID: <CAA93jw59NuipLDtEASU-E2YYF=FymY-4zG4rR+n1j70shkVFzA@mail.gmail.com> (raw)
I have been sitting here looking at wifi air packet captures off and
on for years now, trying to come up with a representation, over time,
of what the actual airtime usage (and one day, fairness) would look
like. Believe me, looking at the captures is no fun, and (for example)
wireshark tends to misinterpret unreceived retries at different rates
inside a txop as tcp retries (which, while educational, makes it hard
to see actual retries)...
Finally today, I found a conceptual model that "fits" - and it's kind
of my hope that something already out there does this from packet
captures. (?) Certainly there are lots of great pie chart tools out
there...
Basically you start with a pie chart representing a fixed amount of
time - say, 128ms. Then for each device transmitting you assign a
slice of the pie for the amount of airtime used. Then, you can show
the amount of data transmitted in that piece of the pie by increasing
the volume plotted for that slice of the pie. And you sweep around
continually (like a radar scanning or a timepiece's pointer) to show
progress over time, and you show multicast and other traffic as eating
the whole pie for however long it lasts.
conceptually it looks a bit like this:
http://blog.cerowrt.org/images/fairness.png (I borrowed this graph
from http://www.webdesignerdepot.com/2013/11/easily-create-stunning-animated-charts-with-chart-js/
)
Another way to do it would be to have the pie represent all the
stations on the network, and to have the "sweep hand" jump between
them...
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next reply other threads:[~2016-04-18 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 22:35 Dave Taht [this message]
2016-04-18 22:48 ` David Lang
2016-04-18 23:02 ` Bob McMahon
2016-04-18 23:36 ` Dave Taht
2016-04-18 23:11 ` David Lang
2016-04-18 23:50 ` Dave Taht
2016-04-19 0:01 ` David Lang
2016-04-19 0:07 ` Dave Taht
2016-04-19 0:32 ` David Lang
2016-04-18 23:02 ` Isaac Konikoff
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='CAA93jw59NuipLDtEASU-E2YYF=FymY-4zG4rR+n1j70shkVFzA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=make-wifi-fast@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