From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bloat Digest, Vol 29, Issue 6
Date: Mon, 06 May 2013 15:50:07 -0400 [thread overview]
Message-ID: <5188096F.20804@rogers.com> (raw)
In-Reply-To: <mailman.9.1367866802.30731.bloat@lists.bufferbloat.net>
Oliver Hohlfeld wrote:
>> In ascii art, it might look like this:
>> ======++++++++++++
>> - +
>> - +
>> - +
>> - +
> What exactly does this plot represent and on what measurement
> data is it based on? What is your definition of "good" and "bad"?
> Just response times? Where does it's shape comes from?
>
> Before (again) diving into debates on how bufferbloat marketing plots
> should look like, I think we need to make sure that the marketing
> is backed up by empirical data.
>
> --Oliver
It's the inverse of a response time versus load graph for two cases, one
with a very early degradation, the other with a normal one. It's a
bowdlerized version of some real measurements of a REST-based system
with and without a bug. I see the list software put in a link to the
gif, so look at that: it's far better than my hack at "art".
Good and bad are indeed defined in terms of response time for a
request-replay pair, with the appropriate units being part of my question.
The normal shape of a response-time curve is a "hockey stick", like
"_/". Technically it's a hyperbola with it's legs asymptotic to a pair
of straight lines, one line horizontal at the value for load=1, and the
second slanted at an angle that depends on the response time, the
bottleneck time (if different), the think time between requests and the
load. The right-side-up graph uses normal time units.
I tried the experiment of inverting it and asking Dave and the list for
an opinion on units: in my actual example they were normalized by
dividing by the minimum response time, making it non-dimensional.
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
(416) 223-8968
parent reply other threads:[~2013-05-06 19:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.9.1367866802.30731.bloat@lists.bufferbloat.net>]
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=5188096F.20804@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.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