General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] marketing #102 - giving netperf-wrapper a better name?
Date: Thu, 12 Mar 2015 16:31:25 -0700	[thread overview]
Message-ID: <550221CD.8030606@hp.com> (raw)
In-Reply-To: <CAA93jw523E4iF9HNir+QdsMF1twKPM8HhXTjXPdY7NmQKL3g_A@mail.gmail.com>

On 03/12/2015 04:01 PM, Dave Taht wrote:
> 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"'
>
> Hmm...  we need a name with more foo, for sure, a better, more
> descriptive name. Anyone got any ideas? Maybe run a contest somewhere?

Well, not that I dislike the "netperf" name :) but I'll toss a few 
stripes onto the bikeshed:

*) bloat-probe
*) tortoise (ok, it is measuring bloat/latency not speed but still)
*) BMI (Bloat Measurement Index/Investigator/Illuminator ?-)
*) bloat-watcher
*) bloat-finder
*) bloated
*) blubber
*) Ahab

rick

> One (technical) hope would be to find a good file extension for the
> output, so it could be more easily parsed by browsers... but to heck
> with that... a better name?
>
> Toke had some ideas also:
>
> - NQT - http://acronyms.thefreedictionary.com/NQT - I especially like
>    "Not Quite There". nqt.org points to this: http://dyslexiafoundation.org/nqt/
>
> - NetQual - http://www.qoesystems.com/NETQUAL.html
>
> - NQ-tester - doesn't seem to be taken by anything obvious
>
>


  parent reply	other threads:[~2015-03-12 23:31 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 ` Rick Jones [this message]
2015-03-12 23:48   ` [Bloat] " 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
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=550221CD.8030606@hp.com \
    --to=rick.jones2@hp.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