From: Jonathan Morton <chromatix99@gmail.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] marketing #102 - giving netperf-wrapper a better name?
Date: Fri, 20 Mar 2015 22:25:44 +0200 [thread overview]
Message-ID: <2584B47E-BBE6-491E-BE44-8BA4E5075085@gmail.com> (raw)
In-Reply-To: <AE7F97DB5FEE054088D82E836BD15BE931975830@xmb-aln-x05.cisco.com>
> On 20 Mar, 2015, at 22:08, Bill Ver Steeg (versteb) <versteb@cisco.com> wrote:
>
> We should call the metric "sucks-less". As in "Box A sucks less than Box B", or "Box C scored a 17 on the sucks less test".
I suspect real marketing drones would get nervous at a negative-sounding name.
My idea - which I’ve floated in the past, more than once - is that the metric should be “responsiveness”, measured in Hertz. The baseline standard would be 10Hz, corresponding to a dumb 100ms buffer. Get down into the single-digit millisecond range, as fq_codel does, and the Responsiveness goes up above 100Hz, approaching 1000Hz.
Crucially, that’s a positive sort of term, as well as trending towards bigger numbers with actual improvements in performance, and is thus more potentially marketable.
- Jonathan Morton
next prev parent reply other threads:[~2015-03-20 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 23:01 Dave Taht
2015-03-12 23:04 ` [Bloat] [Cerowrt-devel] " Toke Høiland-Jørgensen
2015-03-12 23:31 ` [Bloat] " Rick Jones
2015-03-12 23:48 ` Dave Taht
2015-03-13 0:10 ` Dave Taht
2015-03-13 7:07 ` Rémi Cardona
2015-03-20 20:08 ` Bill Ver Steeg (versteb)
2015-03-20 20:25 ` Jonathan Morton [this message]
2015-03-20 21:08 ` Bill Ver Steeg (versteb)
2015-03-21 0:19 ` [Bloat] [Cerowrt-devel] " David P. Reed
2015-03-21 11:35 ` [Bloat] " Alex Burr
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=2584B47E-BBE6-491E-BE44-8BA4E5075085@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=versteb@cisco.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