General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jonathan Foulkes <jf@jonathanfoulkes.com>
Cc: Dave Taht <dave.taht@gmail.com>,  bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] COTS router with OpenWrt
Date: Mon, 28 Nov 2016 18:40:18 +0100	[thread overview]
Message-ID: <87fumbqz99.fsf@toke.dk> (raw)
In-Reply-To: <E3BC6365-C976-4561-A895-FAD842C4BB69@jonathanfoulkes.com> (Jonathan Foulkes's message of "Mon, 28 Nov 2016 12:16:35 -0500")

Jonathan Foulkes <jf@jonathanfoulkes.com> writes:

> Hi Dave, a special thanks to you for all the cheerleading and pushing you do on this topic.
>
>> I hope that your marketing campaign is being successful on these
>> fronts. It has always been my goal to "enable better products", but
>> not have the headache of making them myself, where 99.99% of the
>> effort is (like in cerowrt), in making everything else "just work" and
>> be reliable enough to ship.
>
> I haven’t ramped up the marketing in a big way yet, but what I am
> doing is quite effective (e.g. click through metrics are 5 to 10x the
> norm); what’s been most astonishing is the word of mouth spread.
>
> Yes, lots of effort in having a reliable, supportable product. 
>
> As you can see from the site, my messaging has been focused on regular
> end users, using terminology they can hopefully grasp (I get accused
> of both being too technical and not technical enough, so maybe I got
> it right ;-)
>
> One area of messaging that I believe members of this list could
> provide input on is around how to get people to understand that
> ‘speed’ (line capacity) is not everything. I keep looking for ways to
> address that and wrote a short post on it:
> http://evenroute.com/the-last-50-feet/quick-vs-fast

Well, there's Stuart's classic rant from two decades ago (which is on
the technical side):
http://www.stuartcheshire.org/rants/Latency.html

On the less technical side, there's this video from the RITE project:
https://www.youtube.com/watch?v=F1a-eMF9xdY

And this one that nicely showcases latency, but then draws the wrong
conclusion (that you need more bandwidth to fix it):
https://www.youtube.com/watch?v=_fNp37zFn9Q

-Toke

  reply	other threads:[~2016-11-28 17:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26 14:08 Rich Brown
2016-11-26 14:45 ` Jonathan Foulkes
2016-11-26 19:56 ` Jonathan Morton
2016-11-28 15:21 ` Jonathan Foulkes
2016-11-28 15:57   ` Dave Taht
2016-11-28 17:16     ` Jonathan Foulkes
2016-11-28 17:40       ` Toke Høiland-Jørgensen [this message]
2016-11-28 17:41   ` [Bloat] How to "sell" improvement (was: COTS router with OpenWrt) David Collier-Brown
2016-11-28 17:59     ` [Bloat] How to "sell" improvement Kathleen Nichols
2016-11-28 18:37       ` David Collier-Brown
2016-11-28 18:58         ` Simon Barber
2016-11-28 19:25           ` David Collier-Brown
2016-11-28 19:40             ` David Lang
2016-12-04 16:08               ` Jonathan Foulkes
2016-12-04 22:32                 ` David Lang
2016-11-28 19:26         ` Jonathan Morton
2016-11-28 19:42           ` David Collier-Brown

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=87fumbqz99.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=jf@jonathanfoulkes.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