From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Sidebar re illustrating quality (was: New Version Notification for draft-cpaasch-ippm-responsiveness-00.txt)
Date: Thu, 19 Aug 2021 14:17:15 -0700 [thread overview]
Message-ID: <6C2AF637474AE2E1E8AC10A0@[192.168.1.16]> (raw)
In-Reply-To: <80e0a336-06e4-c6b6-a01b-f849296086a6@indexexchange.com>
--On Thursday, August 19, 2021 2:50 PM -0400 Dave Collier-Brown
<dave.collier-brown@indexexchange.com> wrote:
> I can't actually draw a picture of it here, but there's a good way to
> show multiple limiting factor graphically. One is with a bucket,
> http://www.imthird.org/the-limiting-factor-concept, but for comparisons
> I like a simpler one
>
> For an example, imagine a large letter "Y" with the stem labelled
> "throughput", one arm labelled "latency" and the other "RPM". There's a
> dotted-line circle drawn over it so that the two arms touch the circle,
> and the stem sticks out through it.
>
> The diameter of the circle is the "goodness" of the connection, and you
> can line up diagrams like this for Bell, Rogers and Telus and see that
> they all have fine throughput but lousy latency and RPM. And it extends
> to multiple dimensions as well as multiple suppliers, so you could have
> a five-legged Y if you wanted. I like three, myself.
>
> I first saw this used for nutrients in the first edition of "Diet for a
> Small Planet", but the editors found it too nerdy and talked the author
> into taking it out (:-()
American innumeracy is so frustrating.
Do you have a link to the "Y" illustration? I'm having trouble visualizing
it. Is the Y inverted? I don't understand what you mean by the stem going
through the circle if the arms are touching it, or what the stem means.
next prev parent reply other threads:[~2021-08-19 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 21:41 [Bloat] Fwd: New Version Notification for draft-cpaasch-ippm-responsiveness-00.txt Christoph Paasch
2021-08-15 13:39 ` Erik Auerswald
2021-08-18 22:01 ` Christoph Paasch
2021-08-19 7:17 ` Erik Auerswald
2021-08-19 15:48 ` Christoph Paasch
2021-08-19 17:50 ` [Bloat] Sidebar re illustrating quality (was: New Version Notification for draft-cpaasch-ippm-responsiveness-00.txt) Dave Collier-Brown
2021-08-19 21:17 ` Kenneth Porter [this message]
2021-08-20 1:58 ` Dave Collier-Brown
2021-08-21 1:22 ` Kenneth Porter
2021-08-21 11:01 ` Sebastian Moeller
2021-08-21 10:23 ` Erik Auerswald
2021-08-21 16:31 ` Dave Collier-Brown
2021-09-21 20:50 ` [Bloat] [ippm] Fwd: New Version Notification for draft-cpaasch-ippm-responsiveness-00.txt Toerless Eckert
2021-10-22 23:19 ` Christoph Paasch
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='6C2AF637474AE2E1E8AC10A0@[192.168.1.16]' \
--to=shiva@sewingwitch.com \
--cc=bloat@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