General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: john <email@matrix8.org>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Terminology for Laypeople
Date: Sun, 16 May 2021 22:20:19 +0300	[thread overview]
Message-ID: <487B5EAD-6FEE-482C-919E-D1F1B7166530@gmail.com> (raw)
In-Reply-To: <C9ED74A8420E7CEE7927C74@matrix8.org>

> On 16 May, 2021, at 9:48 pm, john <email@matrix8.org> wrote:
> 
> After watching Dave's YouTube video, it seems to me, the congestion of 
> the packets which Dave was explaining is equivalent to sushi plats on 
> conveyor stuck on the route and colliding each other on the conveyor 
> since the conveyor keeps bringing more packets one after another to the 
> collision point, then plats overflow from the conveyor and dropped on 
> the floor.
> 
> So now, my question is the picture I described above is close to what 
> bufferbloat is? Or I am still very far from understanding? If I am still 
> far from understanding, will you be able to explain it to me, the 
> laypeople, using the sushi or donuts conveyor? Is the problem the speed 
> adjustment of the conveyor? Or too many plates or donuts are placed on 
> the conveyor? If so, why the rate or speed of each factors can not be 
> adjusted? I even wonder if you could explain it using the door to door 
> package delivery service since you are talking about delivering packets.

Here's an analogy for you:

Today there is a logging operation going on just up the road - not unusual in my part of the world.  They have a team felling trees, another team trimming off the branches, and the trunks are then stacked for later delivery to the sawmill (*much* later - they have to season first).  The branches are fed into a chopping machine which produces firewood and mulch, which is then weighed and bagged for immediate sale.

I need firewood for my sauna stove.  I know that if I load my trailer full of firewood, it'll last me about a year.  I figure I'll pay these guys a visit, and it shouldn't take more than half an hour of my time to get what I need.

Under normal circumstances, that would be true.  However, the hardware store in the town an hour away has also chosen today to replenish its stock of firewood, and they have a representative on site who's basically buying the branches from every tree as it comes down; every so often a big van turns up and collects the product.  He graciously lets me step in and buy the branches off one tree for my own use, and they're tagged as such by the loggers.

So instead of just loading ready-made bags of firewood into my trailer, I have to wait for the trimming team to get around to taking the branches off "my" tree which is waiting behind a dozen others.  The branches then go into a big stack of branches waiting for the chopping machine.  When they eventually get around to chopping those, the firewood is carefully put in a separate pile, waiting for the weighing and bagging.

It takes a full hour before I have the branches from "my" tree in a useful format for firing a sauna stove and in my trailer.  Which is now only half full.  To fill it completely, I have to go through the entire process again from the beginning - only the felling team has been going gangbusters and there are now *twenty* trees waiting for trimming.

I planned for half an hour.  It actually took me three hours to get my firewood.  Not for lack of throughput - that was one pretty effective logging operation - but because of the *queues*.

 - Jonathan Morton

  reply	other threads:[~2021-05-16 19:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 15:50 Ingemar Johansson S
2021-05-12 21:51 ` Dave Collier-Brown
2021-05-16 18:48   ` john
2021-05-16 19:20     ` Jonathan Morton [this message]
2021-05-16 20:44       ` Michael Richardson
2021-05-16 21:32         ` Aaron Wood
2021-05-16 21:33         ` Jonathan Morton
2021-05-16 23:02           ` Jonathan Morton
2021-05-17  5:18     ` Simon Barber
2021-05-17  5:24       ` Jonathan Morton
  -- strict thread matches above, loose matches on Subject: below --
2021-05-05  0:02 Livingood, Jason
2021-05-05  0:14 ` James R Cutler
2021-05-05  7:41   ` Erik Auerswald
2021-05-06 14:38     ` Dave Taht
2021-05-05  1:41 ` Matt Mathis
2021-05-05 15:05 ` Neil Davies
2021-05-06 13:23 ` Jason Iannone
2021-05-06 13:40   ` David Lang
2021-05-06 18:00     ` Dave Taht
2021-05-10 20:10 ` Jonathan Foulkes
2021-05-11 21:26   ` Greg White

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=487B5EAD-6FEE-482C-919E-D1F1B7166530@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=email@matrix8.org \
    /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