From: Jonathan Morton <chromatix99@gmail.com>
To: Matt Mathis <mattmathis@google.com>
Cc: dave.collier-brown@indexexchange.com,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Rpm] Airbnb
Date: Tue, 10 Aug 2021 14:51:38 +0300 [thread overview]
Message-ID: <AE016316-78D1-475F-83B1-0700823B3D8F@gmail.com> (raw)
In-Reply-To: <CAH56bmDSgDtpV_nebP=d6dNZD5N30zJN-Ed=ot4-oycmBiMJvQ@mail.gmail.com>
> On 10 Aug, 2021, at 7:51 am, Matt Mathis via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> For years we published a "jitter" metric that I considered to be bogus, basically max_rtt - min_rtt, (which were builtin Web100 instruments).
>
> In 2019, we transitioned from web100 to "standard" linux tcp_info, which does not capture max_rtt. Since the web100 jitter was viewed as bogus, we did not attempt to reconstruct it, although we could have. Designing and implementing a new latency metric was on my todo list from the beginning of that transition, but chronically preempted by more pressing problems.
>
> It finally made it to the top of my queue which is why I am suddenly not lurking here and the new rpm list. I was very happy to see the Apple responsiveness metric, and realized that M-Lab can implement a TCP version of it, that can be computed both in real time on future tests and retroactively over archived tests collected over the last 12 years.
>
> This quick paper might be of interest: Preliminary Longitudinal Study of Internet Responsiveness
Intriguing. The properly processed version of the data will probably show the trends more clearly, too.
I think there is merit in presenting the European data as well, so long as the discontinuities caused by topological/geographical alterations can be identified and indicated. There are some particular local phenomena that I think would be reflected in that, such as the early rollout of fq_codel by free.fr.
- Jonathan Morton
next prev parent reply other threads:[~2021-08-10 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BY5PR11MB42574D4BBC71FF2049F7E544DEEC9@BY5PR11MB4257.namprd11.prod.outlook.com>
2021-08-07 18:57 ` [Bloat] Fwd: Airbnb Dave Taht
2021-08-09 16:44 ` [Bloat] [Rpm] Airbnb oesh
2021-08-09 19:25 ` Dave Collier-Brown
2021-08-09 20:24 ` Jonathan Morton
2021-08-10 0:27 ` Dave Collier-Brown
2021-08-10 4:51 ` Matt Mathis
2021-08-10 11:51 ` Jonathan Morton [this message]
2021-08-13 18:58 ` Livingood, Jason
2021-08-16 17:00 ` Matt Mathis
2021-08-13 18:56 ` [Bloat] Fwd: Airbnb Livingood, Jason
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=AE016316-78D1-475F-83B1-0700823B3D8F@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.collier-brown@indexexchange.com \
--cc=mattmathis@google.com \
/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