From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Rémi Cardona" <remi@gentoo.org>,
bloat <bloat@lists.bufferbloat.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] marketing #102 - giving netperf-wrapper a better name?
Date: Fri, 20 Mar 2015 20:08:43 +0000 [thread overview]
Message-ID: <AE7F97DB5FEE054088D82E836BD15BE931975830@xmb-aln-x05.cisco.com> (raw)
In-Reply-To: <55028CB6.80101@gentoo.org>
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".
The actual measurement would be the number of milliseconds of additional queueing delay when the system is congested, but most people will not take the time to look under the covers. Maybe the term "lags-less" would be better..
Easy to understand, and it gives the proper nudge.
Bill VerSteeg
-----Original Message-----
From: bloat-bounces@lists.bufferbloat.net [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of Rémi Cardona
Sent: Friday, March 13, 2015 3:08 AM
To: bloat; cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Bloat] marketing #102 - giving netperf-wrapper a better name?
Le 13/03/2015 00:01, Dave Taht a écrit :
> as netperf-wrapper has grown to include far more tests than netperf,
> with quite a few more on their way, calling it this is increasingly
> less appropriate:
>
> A noted cynic wrote me privately last month, about netperf-wrapper:
>
> 'why don't you rename the friggin thing "bufferbloat" or "bloattest"
> or something? Netperf-wrapper is a terrible name, seemingly still
> whatever the programmer called it when he wrote the first sketchy
> version, one step up from "foo"'
Bloatalyzer ?
Cheers,
Rémi
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2015-03-20 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 23:01 [Cerowrt-devel] " Dave Taht
2015-03-12 23:04 ` Toke Høiland-Jørgensen
[not found] ` <550221CD.8030606@hp.com>
[not found] ` <CAA93jw7tdVUV70P8CtC4U5ALmtwrU5XtX8oSpdg_PtN+Z9HetA@mail.gmail.com>
2015-03-13 0:10 ` [Cerowrt-devel] [Bloat] " Dave Taht
2015-03-13 7:07 ` Rémi Cardona
2015-03-20 20:08 ` Bill Ver Steeg (versteb) [this message]
2015-03-20 20:25 ` Jonathan Morton
2015-03-20 21:08 ` Bill Ver Steeg (versteb)
2015-03-21 0:19 ` David P. Reed
2015-03-21 11:35 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AE7F97DB5FEE054088D82E836BD15BE931975830@xmb-aln-x05.cisco.com \
--to=versteb@cisco.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=remi@gentoo.org \
/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