From: Rich Brown <richb.hanover@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Best Bufferbloat Analogy - Ever (was: FCC Input)
Date: Sat, 27 Mar 2021 18:42:04 -0400 [thread overview]
Message-ID: <0AC911C3-F385-4D4A-AD7F-0CB5947A9963@gmail.com> (raw)
In-Reply-To: <mailman.2443.1616835248.24343.bloat@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
> On Mar 27, 2021, at 4:54 AM, bloat-request@lists.bufferbloat.net wrote:
>
> Jitter and bloat aren't intuitive and need a lot more thinking and patience
> to understand. Perhaps we need a good animated cartoon to explain it.
I recently riffed off the Waveform bufferbloat test (https://www.waveform.com/tools/bufferbloat#question-0) that includes, "Can you explain bufferbloat like I'm five?"
My blog posting (complete with a SmartSink(tm)) is at: https://randomneuronsfiring.com/best-bufferbloat-analogy-ever/
Maybe that's a start toward an animation...
Rich
[-- Attachment #2: Type: text/html, Size: 2828 bytes --]
parent reply other threads:[~2021-03-27 22:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.2443.1616835248.24343.bloat@lists.bufferbloat.net>]
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=0AC911C3-F385-4D4A-AD7F-0CB5947A9963@gmail.com \
--to=richb.hanover@gmail.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