From: Dave Crocker <dhc@dcrocker.net>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] I keep hoping that we will turn this corner
Date: Sat, 1 Jun 2024 08:24:28 -0700 [thread overview]
Message-ID: <26794f65-08a1-403e-a69d-530c6e481cb2@dcrocker.net> (raw)
In-Reply-To: <CAA93jw7fEMcgOw1YstWCwKcPJvwn0PF+L9eqvM0HM0BsUn9S-w@mail.gmail.com>
On 6/1/2024 7:48 AM, Dave Taht via Nnagain wrote:
> https://randomneuronsfiring.com/all-the-reasons-that-bufferbloat-isnt-a-problem/
>
A curse of being bright is failing to recognize when we aren't. If only
there were a term for that...
Some decades back, I heard Kleinrock give a summary of queuing theory
research where he reduced it to a graph. Throughput vs. latency. The
curve was almost flat, rising only slightly, until the knee of the
curve, which was quite sharp, going to almost vertical. He noted that
the math for this was complicated but the summary description was not:
"Things are very, very good, until they are very very bad. When they are
good, you don't need queuing. When they are bad, queuing won't help;
you need more capacity. Queuing is for the brief and occasional period
within the knee of the curve."
If it ain't transient then queuing isn't the answer. If it is
transient, you don't need lots of buffering.
Systems thinking is not natural for most of us, and bufferbloat is an
example of local optimization without attention to systems effects. For
the list of push-backs your article cites, that lack of attention is due
to excessive faith in entirely misguided intuitions.
Systems thinking requires quite a bit of skepticism about intuitions.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
mast:@dcrocker@mastodon.social
next prev parent reply other threads:[~2024-06-01 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 14:48 Dave Taht
2024-06-01 15:24 ` Dave Crocker [this message]
2024-06-01 17:39 ` Robert McMahon
2024-06-02 2:35 ` Dave Crocker
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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26794f65-08a1-403e-a69d-530c6e481cb2@dcrocker.net \
--to=dhc@dcrocker.net \
--cc=dcrocker@bbiw.net \
--cc=nnagain@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