General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
	Greg White <g.white@cablelabs.com>,
	 Jonathan Foulkes <jf@jonathanfoulkes.com>,
	bloat <bloat@lists.bufferbloat.net>,
	Bob McMahon <bob.mcmahon@broadcom.com>
Subject: Re: [Bloat] [EXTERNAL] Re: Terminology for Laypeople
Date: Wed, 12 May 2021 09:40:46 -0700	[thread overview]
Message-ID: <CAA93jw5crwckS1JHh-TVqciDB7QfvyPWdnV_Vm464k-z9ivbUA@mail.gmail.com> (raw)
In-Reply-To: <13254.1620835357@localhost>

On Wed, May 12, 2021 at 9:02 AM Michael Richardson <mcr@sandelman.ca> wrote:
>
> The part I'd like to simplify is "latency"....
> Most people can understand that the hot water tap doesn't produce hot water
> instantly, but I don't know how leverage that experience to networking directly.
> Idle and Working are good.

The demo I did in my broadcom preso ages back was the simplest I could imagine,
but not on the slides. ( http://www.taht.net/~d/broadcom_aug9_2018.pdf  )

I brought a coffee pot, a large carafe, two differently sized funnels,
an eye dropper, (and a towel!)

and showed how sending more data at the sender didn't change the
receiving rate, and how a human,
at least, reacted to tail "packet loss" by slowing down.

It strikes me that this demo is amiable to doing via videoconference.
Perhaps something that floats could be used to represent voip, like a
dried pea.

Being a perfectionist, I've not liked that this demo does not also
represent what happens when the upstream link
is clogged, but perhaps with some video trickery... (there's
videoconferencing filters for inverting the video), and intensely
dislike that it doesn't at all cover how RTT on every packet is the
driver but but that would require a water fountain as per VJ's big
demo at IETF 84.

We'd done a lot of more complicated vids than this (my modena talk,
shemminger's linux plumbers talk) trying to then explain aqm and fq,
but it seems like this mere starting point would be a useful visual
aid nowadays for laypeople.

https://courses.cs.washington.edu/courses/cse550/14au/papers/CSE550.congavoid.pdf
for engineers.

>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat



-- 
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/

Dave Täht CTO, TekLibre, LLC

  reply	other threads:[~2021-05-12 16:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 13:22 Livingood, Jason
2021-05-12 16:02 ` Michael Richardson
2021-05-12 16:40   ` Dave Taht [this message]
2021-05-12 21:10     ` Michael Richardson
2021-05-14  3:47       ` Bob McMahon
2021-05-16 18:07       ` Jonathan Morton
2021-05-17 21:27         ` Matt Mathis
2021-05-18  0:47           ` Bob McMahon
2021-05-18  6:31           ` Neil Davies
2021-05-18 15:24             ` Matt Mathis
2021-05-18 20:59             ` Bob McMahon
2021-05-18 22:29               ` David Lang
2021-05-19  0:02                 ` Bob McMahon

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=CAA93jw5crwckS1JHh-TVqciDB7QfvyPWdnV_Vm464k-z9ivbUA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=Jason_Livingood@comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=bob.mcmahon@broadcom.com \
    --cc=g.white@cablelabs.com \
    --cc=jf@jonathanfoulkes.com \
    --cc=mcr@sandelman.ca \
    /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