From: Neil Davies <neil.davies@pnsol.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>, Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] [Bloat] infinite queue
Date: Thu, 11 May 2023 21:00:00 +0100 [thread overview]
Message-ID: <FB1F8C98-668C-485F-9881-43183351632D@pnsol.com> (raw)
In-Reply-To: <CAA93jw5JCvzVzuAMhU-kam_sAznnT4cQ_W6xud_xTySaQA-mjw@mail.gmail.com>
There was an idea (I think from the 1970’s) that is refinement of this - isometric flow control.
I would say that the key notion (expressed here) is that the ‘work in progress’ is finite - the isometric concept is a refinement on that, in that it says “there is some number”.
Also, subtly implicit in this article is that the best you can aspire to is 80% loading. Using the isometric concept (carefully!) I’ve help create system that can predictably operate at high 90% loading.
Limiting the work-in-progress ensures a bound on the response-delay.
Neil
> On 11 May 2023, at 00:39, Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> nice blog post from someone new about the infinite queue problem, with
> a clean example:
>
> https://brooker.co.za/blog/2023/05/10/open-closed.html
>
> --
> Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
> Dave Täht CSO, LibreQos
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2023-05-11 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 23:39 [Rpm] " Dave Taht
2023-05-11 20:00 ` Neil Davies [this message]
2023-05-12 15:46 ` [Rpm] iperf 2 bounceback - independent request/reply sizes rjmcmahon
2023-05-12 15:53 ` Sebastian Moeller
2023-05-12 16:02 ` rjmcmahon
2023-05-12 20:39 ` rjmcmahon
2023-05-12 16:00 ` rjmcmahon
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FB1F8C98-668C-485F-9881-43183351632D@pnsol.com \
--to=neil.davies@pnsol.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=rpm@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