General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Foulkes <jf@jonathanfoulkes.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] keeping the lights on at bufferbloat.net
Date: Tue, 5 Feb 2019 08:45:28 -0500	[thread overview]
Message-ID: <8725A111-1411-418A-99C9-E36E52C2B512@jonathanfoulkes.com> (raw)
In-Reply-To: <87bm3qhb8c.fsf@toke.dk>

Thanks for sharing that Toke, it is a very good animated explainer. I’ll be linking to it in some of my FAQ’s and articles.

A key point of this video is to illustrate capacity with large vehicles, that move much content, but themselves do not have ‘quick’ transit, or round-trip times. That correlates nicely with the metrics for RTT and CWND in speedtests.

Examples focusing on ’top-speed’ of vehicles is missing a bit of the point that Internet ’speed’ metric is truly more about capacity rather than responsiveness. I’ll be re-thinking the use of those.

Cheers,

Jonathan

> On Feb 5, 2019, at 3:48 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> Jonathan Foulkes <jf@jonathanfoulkes.com> writes:
> 
>> One analogy I’m have her illustrate depicts an ambulance vs a Ferrari
>> getting through traffic. The ’slower’ one has an advantage, it has
>> traffic rules on its side ;-)
> 
> The RITE project already did the F1 car vs bus in their video back in
> 2014: https://www.youtube.com/watch?v=F1a-eMF9xdY
> 
> I like the ambulance analogy, though :)
> 
> -Toke


      reply	other threads:[~2019-02-05 13:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 16:55 Dave Taht
2019-02-04 17:13 ` Jonathan Foulkes
2019-02-04 19:09   ` Dave Taht
2019-02-04 20:29     ` Dave Taht
2019-02-04 22:03       ` Jonathan Foulkes
2019-02-05  8:48         ` Toke Høiland-Jørgensen
2019-02-05 13:45           ` Jonathan Foulkes [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=8725A111-1411-418A-99C9-E36E52C2B512@jonathanfoulkes.com \
    --to=jf@jonathanfoulkes.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=toke@toke.dk \
    /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