From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "MORTON JR., AL" <acmorton@att.com>,
Rpm <rpm@lists.bufferbloat.net>,
ippm@ietf.org
Subject: Re: [Rpm] lightweight active sensing of bandwidth and buffering
Date: Tue, 01 Nov 2022 16:39:48 -0700 [thread overview]
Message-ID: <344f2a33b6bcae4ad4390dcb96f92589@rjmcmahon.com> (raw)
In-Reply-To: <CAA93jw6kuHJp_PnUBb6J4HiFmy=xTG9uiu7bML7fuHFzNhMr2w@mail.gmail.com>
Bufferbloat shifts the minimum of the latency or OWD CDF. A suggestion
is to disable x-axis auto-scaling and start from zero.
Bob
> For about 2 years now the cake w-adaptive bandwidth project has been
> exploring techniques to lightweightedly sense bandwidth and buffering
> problems. One of my favorites was their discovery that ICMP type 13
> got them working OWD from millions of ipv4 devices!
>
> They've also explored leveraging ntp and multiple other methods, and
> have scripts available that do a good job of compensating for 5g and
> starlink's misbehaviors.
>
> They've also pioneered a whole bunch of new graphing techniques, which
> I do wish were used more than single number summaries especially in
> analyzing the behaviors of new metrics like rpm, samknows, ookla, and
> RFC9097 - to see what is being missed.
>
> There are thousands of posts about this research topic, a new post on
> OWD just went by here.
>
> https://forum.openwrt.org/t/cake-w-adaptive-bandwidth/135379/793
>
> and of course, I love flent's enormous graphing toolset for simulating
> and analyzing complex network behaviors.
next prev parent reply other threads:[~2022-11-01 23:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CH0PR02MB79808E2508E6AED66DC7657AD32E9@CH0PR02MB7980.namprd02.prod.outlook.com>
[not found] ` <CH0PR02MB7980DFB52D45F2458782430FD3379@CH0PR02MB7980.namprd02.prod.outlook.com>
[not found] ` <CH0PR02MB7980D3036BF700A074D902A1D3379@CH0PR02MB7980.namprd02.prod.outlook.com>
2022-10-31 16:52 ` [Rpm] [ippm] Preliminary measurement comparison of "Working Latency" metrics Dave Taht
2022-10-31 18:52 ` rjmcmahon
2022-10-31 22:08 ` MORTON JR., AL
2022-10-31 22:44 ` rjmcmahon
2022-11-01 20:15 ` [Rpm] lightweight active sensing of bandwidth and buffering Dave Taht
2022-11-01 23:39 ` rjmcmahon [this message]
2022-11-02 8:23 ` Sebastian Moeller
2022-11-02 9:41 ` [Rpm] [ippm] " Ruediger.Geib
2022-11-02 19:29 ` rjmcmahon
2022-11-02 19:44 ` Dave Taht
2022-11-02 20:37 ` rjmcmahon
2022-11-02 21:13 ` Sebastian Moeller
2022-11-02 21:41 ` Sebastian Moeller
2022-11-03 8:20 ` Ruediger.Geib
2022-11-03 8:57 ` Sebastian Moeller
2022-11-03 11:25 ` Ruediger.Geib
2022-11-03 11:48 ` Sebastian Moeller
2022-11-02 19:21 ` [Rpm] " rjmcmahon
2022-10-31 20:40 ` [Rpm] [ippm] Preliminary measurement comparison of "Working Latency" metrics MORTON JR., AL
2022-10-31 23:30 ` Dave Taht
2022-11-01 4:21 ` Dave Taht
2022-11-01 14:51 ` MORTON JR., AL
2022-11-04 17:14 ` MORTON JR., AL
2022-11-04 18:12 ` rjmcmahon
2022-11-04 18:58 ` MORTON JR., AL
2022-11-04 19:10 ` Sebastian Moeller
2022-11-05 19:36 ` MORTON JR., AL
2022-12-11 19:21 ` MORTON JR., AL
2022-12-12 2:38 ` Dave Taht
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=344f2a33b6bcae4ad4390dcb96f92589@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=acmorton@att.com \
--cc=dave.taht@gmail.com \
--cc=ippm@ietf.org \
--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