From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Bob McMahon <bob.mcmahon@broadcom.com>,
Tim Higgins <tim@smallnetbuilder.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] SmallNetBuilder article: Does OFDMA Really Work?
Date: Fri, 15 May 2020 22:38:40 +0200 [thread overview]
Message-ID: <87k11dq6gf.fsf@toke.dk> (raw)
In-Reply-To: <mailman.342.1589573120.24343.make-wifi-fast@lists.bufferbloat.net>
Bob McMahon via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net>
writes:
> In that analogy, latency and bloat, while correlated, aren't the same
> thing. I think by separating them one can better understand how a system
> will perform. I suspect your tests with 120ms of latency are really
> measuring bloat. Little's law is average queue depth = average effective
> arrival rate * average service time. Bloat is mostly about excessive queue
> depths and latency mostly about excessive service times. Since they affect
> one another it's easy to conflate them.
I'd say this is a bit of an odd definition? In my view, "latency" is the
time it takes a packet to get from one place to another, and it can have
many sources, one of which is bloat. For a rather comprehensive survey
and categorisation of other sources, see [0].
As you say, bloat does tend to drown out other sources of latency, but
that is a bug as far as I'm concerned. Once you fix that, looking at all
the other sources becomes much easier. Optimising those other sources of
latency is worthwhile too, of course, it just doesn't help as much until
you also fix the bloat.
-Toke
[0] https://ieeexplore.ieee.org/abstract/document/6967689
next prev parent reply other threads:[~2020-05-15 20:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 16:43 Tim Higgins
2020-05-14 21:38 ` Bob McMahon
2020-05-14 21:42 ` Bob McMahon
2020-05-15 15:20 ` Tim Higgins
2020-05-15 19:36 ` Bob McMahon
2020-05-15 19:50 ` Tim Higgins
2020-05-15 20:05 ` Bob McMahon
2020-05-15 20:24 ` Toke Høiland-Jørgensen
2020-05-15 20:30 ` Dave Taht
2020-05-15 21:35 ` Bob McMahon
2020-05-16 5:02 ` Dave Taht
[not found] ` <mailman.342.1589573120.24343.make-wifi-fast@lists.bufferbloat.net>
2020-05-15 20:38 ` Toke Høiland-Jørgensen [this message]
2020-05-15 6:47 ` Erkki Lintunen
2020-05-15 15:34 ` Tim Higgins
2020-05-15 16:25 ` Dave Taht
2020-05-15 16:41 ` 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=87k11dq6gf.fsf@toke.dk \
--to=toke@redhat.com \
--cc=bob.mcmahon@broadcom.com \
--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