From: Jonathan Morton <chromatix99@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: john <email@matrix8.org>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Terminology for Laypeople
Date: Mon, 17 May 2021 00:33:20 +0300 [thread overview]
Message-ID: <42DC54D2-AC15-455F-B4B1-E97BE05CD00D@gmail.com> (raw)
In-Reply-To: <15155.1621197853@localhost>
> On 16 May, 2021, at 11:44 pm, Michael Richardson <mcr@sandelman.ca> wrote:
>
> Your analogy is definitely the result of optimizing for batches rather than latency.
I really don't know how you got there from here. What I described is basically a pipeline process, not batch processing. The delay is caused by the fact that the product already in the pipeline has already been bought by the hardware store, and thus contractually the loggers can't divert it to an individual customer like me.
You can think of one bag of firewood as representing a packet of data. I've requested a particular number of such bags to fill my trailer. Until my trailer is full, my request is not satisfied. The hardware store is just taking whatever manufacturing capacity is available; their warehouse is *huge*.
We can explore the analogy further by changing some of the conditions:
1: If the felling of trees was the bottleneck of the operation, such that the trimming, chopping and bagging could all keep up with it, then the delay to me would be much less because I wouldn't have to wait for various backlogs (of complete trees, branches, and piles of firewood) belonging to the hardware store to be dealt with first. Processing each tree doesn't take very long, there's just an awful lot of them in this patch of forest.
1a: If the foreman told the felling team to take a tea break when a backlog built up, that would have nearly the same effect. That's what an AQM does.
2: If the hardware store wasn't involved at all, the bags of firewood would be waiting, ready to be sold. I'd be done in the time it took to load the bags into my trailer.
3: If the loggers sold the *output* of the process to the hardware store, rather than having them reserve it at the head of the pipeline, then I might only have to wait for the throughput of of the operation to produce what I needed, and load it directly into my trailer. *That* would be just-in-time manufacturing.
- Jonathan Morton
next prev parent reply other threads:[~2021-05-16 21:33 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
2021-05-16 20:44 ` Michael Richardson
2021-05-16 21:32 ` Aaron Wood
2021-05-16 21:33 ` Jonathan Morton [this message]
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=42DC54D2-AC15-455F-B4B1-E97BE05CD00D@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=email@matrix8.org \
--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