From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Representing normal vs bloated systems in diagrams
Date: Mon, 06 May 2013 10:06:30 +0200 [thread overview]
Message-ID: <51876486.70309@net.t-labs.tu-berlin.de> (raw)
In-Reply-To: <51856AE3.3070401@rogers.com>
> 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
prev parent reply other threads:[~2013-05-06 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7754.1367496260.1742.bloat@lists.bufferbloat.net>
2013-05-04 20:09 ` [Bloat] Representing normal vs bloated systems in diagrams (was: A long-delayed thought on "three bars") David Collier-Brown
2013-05-06 8:06 ` Oliver Hohlfeld [this message]
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=51876486.70309@net.t-labs.tu-berlin.de \
--to=oliver@net.t-labs.tu-berlin.de \
--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