From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Taraldsen Erik <erik.taraldsen@telenor.no>,
Rpm <rpm@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Rpm] [Make-wifi-fast] [Cake] [Bloat] The most wonderful video ever about bufferbloat
Date: Mon, 10 Oct 2022 09:45:31 -0700 [thread overview]
Message-ID: <CAHb6LvqHNv_R2Asn944Kx91Cud5J3XSM-c+PcK8Bz19uaMDynw@mail.gmail.com> (raw)
In-Reply-To: <72674884-9E0D-4645-B5F5-C593CC45A8F0@gmx.de>
[-- Attachment #1.1: Type: text/plain, Size: 4036 bytes --]
I think conflating bufferbloat with latency misses the subtle point in that
bufferbloat is a measurement in memory units more than a measurement in
time units. The first design flaw is a queue that is too big. This youtube
video analogy doesn't help one understand this important point.
Another subtle point is that the video assumes AQM as the only solution and
ignores others, i.e. pacing at the source(s) and/or faster service rates. A
restaurant that let's one call ahead to put their name on the waitlist
doesn't change the wait time. Just because a transport layer slowed down
and hasn't congested a downstream queue doesn't mean the e2e latency
performance will meet the gaming needs as an example. The delay is still
there it's just not manifesting itself in a shared queue that may or may
not negatively impact others using that shared queue.
Bob
On Mon, Oct 10, 2022 at 2:40 AM Sebastian Moeller via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:
> Hi Erik,
>
>
> > On Oct 10, 2022, at 11:32, Taraldsen Erik <erik.taraldsen@telenor.no>
> wrote:
> >
> > On 10/10/2022, 11:09, "Sebastian Moeller" <moeller0@gmx.de> wrote:
> >
> > Nice!
> >
> >> On Oct 10, 2022, at 07:52, Taraldsen Erik via Cake <
> cake@lists.bufferbloat.net> wrote:
> >>
> >> It took about 3 hours from the video was release before we got the
> first request to have SQM on the CPE's we manage as a ISP. Finally
> getting some customer response on the issue.
> >
> > [SM] Will you be able to bump these requests to higher-ups and at
> least change some perception of customer demand for tighter latency
> performance?
> >
> > That would be the hope.
>
> [SM} Excellent, hope this plays out as we wish for.
>
>
> > We actually have fq_codel implemented on the two latest generations of
> DSL routers. Use sync rate as input to set the rate. Works quite well.
>
> [SM] Cool, if I might ask what fraction of the sync are you
> setting the traffic shaper for and are you doing fine grained overhead
> accounting (or simply fold that into a grand "de-rating"-factor)?
>
>
> > There is also a bit of traction around speedtest.net's inclusion of
> latency under load internally.
>
> [SM] Yes, although IIUC they are reporting the interquartile mean
> for the two loaded latency estimates, which is pretty conservative and only
> really "triggers" for massive consistently elevated latency; so I expect
> this to be great for detecting really bad cases, but I fear it is too
> conservative and will make a number of problematic links look OK. But hey,
> even that is leaps and bounds better than the old only idle latency report.
>
>
> > My hope is that some publication in Norway will pick up on that score
> and do a test and get some mainstream publicity with the results.
>
> [SM] Inside the EU the challenge is to get national regulators and
> the BEREC to start bothering about latency-under-load at all, "some
> mainstream publicity" would probably help here as well.
>
> Regards
> Sebastian
>
>
> >
> > -Erik
> >
> >
> >
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #1.2: Type: text/html, Size: 5173 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
next prev parent reply other threads:[~2022-10-10 16:45 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 13:14 [Rpm] " Dave Taht
2022-10-09 13:23 ` [Rpm] [Bloat] " Nathan Owens
2022-10-10 5:52 ` Taraldsen Erik
2022-10-10 9:09 ` [Rpm] [Cake] " Sebastian Moeller
2022-10-10 9:32 ` Taraldsen Erik
2022-10-10 9:40 ` Sebastian Moeller
2022-10-10 11:46 ` [Rpm] [Bloat] [Cake] " Taraldsen Erik
2022-10-10 20:23 ` Sebastian Moeller
2022-10-11 6:08 ` [Rpm] [Cake] [Bloat] " Taraldsen Erik
2022-10-11 6:35 ` Sebastian Moeller
2022-10-11 6:38 ` [Rpm] [Bloat] [Cake] " Dave Taht
2022-10-11 11:34 ` Taraldsen Erik
2022-10-10 16:45 ` Bob McMahon [this message]
2022-10-10 22:57 ` [Rpm] [Bloat] [Make-wifi-fast] " David Lang
2022-10-11 0:05 ` Bob McMahon
2022-10-11 7:15 ` Sebastian Moeller
2022-10-11 16:58 ` Bob McMahon
2022-10-11 17:00 ` Dave Taht
2022-10-11 17:26 ` Sebastian Moeller
2022-10-11 17:47 ` Bob McMahon
2022-10-11 13:57 ` Rich Brown
2022-10-11 14:43 ` [Rpm] [Make-wifi-fast] [Bloat] " Dave Taht
2022-10-11 17:05 ` [Rpm] [Bloat] [Make-wifi-fast] " Bob McMahon
2022-10-11 18:44 ` Rich Brown
2022-10-11 22:24 ` Dave Taht
2022-10-12 17:39 ` Bob McMahon
2022-10-12 21:44 ` [Rpm] [Cake] [Bloat] [Make-wifi-fast] " David P. Reed
2022-10-13 17:45 ` [Rpm] [Bloat] [Make-wifi-fast] [Cake] " Livingood, Jason
2022-10-13 17:49 ` Dave Taht
2022-10-11 6:28 ` [Rpm] [Make-wifi-fast] [Cake] [Bloat] " Sebastian Moeller
2022-10-18 0:02 ` [Rpm] [Make-wifi-fast] " Stuart Cheshire
2022-10-18 2:44 ` Dave Taht
2022-10-18 2:50 ` [Rpm] [Bloat] " Sina Khanifar
2022-10-18 3:15 ` [Rpm] A quick report from the WISPA conference Dave Taht
2022-10-18 17:17 ` Sina Khanifar
2022-10-18 19:04 ` [Rpm] [Bloat] " Sebastian Moeller
2022-10-20 5:15 ` Sina Khanifar
2022-10-20 9:01 ` Sebastian Moeller
2022-10-18 19:17 ` Sebastian Moeller
2022-10-18 2:58 ` [Rpm] [Bloat] [Make-wifi-fast] The most wonderful video ever about bufferbloat David Lang
2022-10-18 17:03 ` [Rpm] [Make-wifi-fast] [Bloat] " Bob McMahon
2022-10-18 18:19 ` Sebastian Moeller
2022-10-18 19:30 ` Bob McMahon
2022-10-19 7:09 ` David Lang
2022-10-19 19:18 ` Bob McMahon
2022-10-19 19:23 ` David Lang
2022-10-19 21:26 ` [Rpm] [Cake] " David P. Reed
2022-10-19 21:37 ` David Lang
2022-10-19 20:44 ` [Rpm] [Make-wifi-fast] " Stuart Cheshire
2022-10-19 21:33 ` [Rpm] [Bloat] " David Lang
2022-10-19 23:36 ` Stephen Hemminger
2022-10-20 14:26 ` [Rpm] [Bloat] [Make-wifi-fast] Traffic analogies (was: Wonderful video) Rich Brown
2022-10-19 21:46 ` [Rpm] [Bloat] [Make-wifi-fast] The most wonderful video ever about bufferbloat Michael Richardson
2022-12-06 19:17 ` [Rpm] [Make-wifi-fast] [Bloat] " Bob McMahon
2022-10-20 9:36 ` [Rpm] [Make-wifi-fast] " Sebastian Moeller
2022-10-20 18:32 ` Stuart Cheshire
2022-10-20 19:04 ` Bob McMahon
2022-10-20 19:12 ` Dave Taht
2022-10-20 19:31 ` Bob McMahon
2022-10-20 19:40 ` Sebastian Moeller
2022-10-21 17:48 ` Bob McMahon
2022-10-20 19:33 ` Sebastian Moeller
2022-10-20 19:33 ` Dave Taht
2022-10-26 20:38 ` Sebastian Moeller
2022-10-26 20:42 ` Dave Taht
2022-10-26 20:53 ` Sebastian Moeller
2022-10-18 18:07 ` [Rpm] [Bloat] " Sebastian Moeller
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=CAHb6LvqHNv_R2Asn944Kx91Cud5J3XSM-c+PcK8Bz19uaMDynw@mail.gmail.com \
--to=bob.mcmahon@broadcom.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=erik.taraldsen@telenor.no \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--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