From: Christoph Paasch <cpaasch@apple.com>
To: nichols@pollere.net
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Ookla - Introducing a Better Measure of Latency
Date: Thu, 12 May 2022 13:00:35 -0700 [thread overview]
Message-ID: <96F2051D-753D-4D67-A6D3-5A053975508C@apple.com> (raw)
In-Reply-To: <c335dcff-6ba3-60a0-838b-4633078985da@pollere.net>
I'm not aware of any rigorous study. But, just from the code, I know ICMP ping in many cases has a different traffic-class and thus implicitly gets quite a different treatment than real traffic.
However, Ookla uses TCP (port 8080) to probe the latency in their app.
Christoph
> On May 12, 2022, at 12:44 PM, Kathleen Nichols <nichols@pollere.net> wrote:
>
> a ping by any other name...
>
> Has anyone ever done a rigorous study to see how well ping delays correspond to the delay that information-carrying packets experience?
>
> On 5/12/22 10:15 AM, Christoph Paasch via Bloat wrote:
>> Ookla's measure of "loaded latency":
>> https://www.ookla.com/articles/introducing-loaded-latency <https://www.ookla.com/articles/introducing-loaded-latency>
>> This will hopefully be a shift in how operators approach the bufferbloat problem.
>> Christoph
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2022-05-12 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 17:15 Christoph Paasch
2022-05-12 19:44 ` Kathleen Nichols
2022-05-12 20:00 ` Christoph Paasch [this message]
2022-05-12 21:04 ` Klatsky, Carl
2022-05-13 7:48 ` Sebastian Moeller
2022-05-13 16:53 ` Christoph Paasch
2022-05-12 20:11 ` Sebastian Moeller
2022-05-13 1:09 ` [Bloat] [Rpm] " Rich Brown
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=96F2051D-753D-4D67-A6D3-5A053975508C@apple.com \
--to=cpaasch@apple.com \
--cc=bloat@lists.bufferbloat.net \
--cc=nichols@pollere.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