From: "Klatsky, Carl" <Carl_Klatsky@comcast.com>
To: Christoph Paasch <cpaasch@apple.com>,
"nichols@pollere.net" <nichols@pollere.net>
Cc: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Ookla - Introducing a Better Measure of Latency
Date: Thu, 12 May 2022 21:04:13 +0000 [thread overview]
Message-ID: <MN2PR11MB4664BD9D41E1AA8435306030A6CB9@MN2PR11MB4664.namprd11.prod.outlook.com> (raw)
In-Reply-To: <96F2051D-753D-4D67-A6D3-5A053975508C@apple.com>
Its good that they are running the latency test also during the load test, but from what it looks like, they seem to be running the latency test to the same server as the load test. I think a more realistic test is to run the load test to one server and the latency test to a different server. That's a more realistic use case...
Regards,
Carl Klatsky
-----Original Message-----
From: Bloat <bloat-bounces@lists.bufferbloat.net> On Behalf Of Christoph Paasch via Bloat
Sent: Thursday, May 12, 2022 4:01 PM
To: nichols@pollere.net
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Ookla - Introducing a Better Measure of Latency
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://urldefense.com/v3/__https://www.ookla.com/articles/introducin
>> g-loaded-latency__;!!CQl3mcHX2A!DHnGDBw2sqsRwHiidAQUOhjXEavZmBOtJKb_IzPhxMm2vqUPyRC2pkVnScJId_KdaNVLsOS7sD0E8QRQ0m8B7LqBavY$ <https://urldefense.com/v3/__https://www.ookla.com/articles/introducing-loaded-latency__;!!CQl3mcHX2A!DHnGDBw2sqsRwHiidAQUOhjXEavZmBOtJKb_IzPhxMm2vqUPyRC2pkVnScJId_KdaNVLsOS7sD0E8QRQ0m8B7LqBavY$ > This will hopefully be a shift in how operators approach the bufferbloat problem.
>> Christoph
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bl
>> oat__;!!CQl3mcHX2A!DHnGDBw2sqsRwHiidAQUOhjXEavZmBOtJKb_IzPhxMm2vqUPyR
>> C2pkVnScJId_KdaNVLsOS7sD0E8QRQ0m8BllXPjdw$
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/blo
> at__;!!CQl3mcHX2A!DHnGDBw2sqsRwHiidAQUOhjXEavZmBOtJKb_IzPhxMm2vqUPyRC2
> pkVnScJId_KdaNVLsOS7sD0E8QRQ0m8BllXPjdw$
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!DHnGDBw2sqsRwHiidAQUOhjXEavZmBOtJKb_IzPhxMm2vqUPyRC2pkVnScJId_KdaNVLsOS7sD0E8QRQ0m8BllXPjdw$
next prev parent reply other threads:[~2022-05-12 21:04 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
2022-05-12 21:04 ` Klatsky, Carl [this message]
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=MN2PR11MB4664BD9D41E1AA8435306030A6CB9@MN2PR11MB4664.namprd11.prod.outlook.com \
--to=carl_klatsky@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cpaasch@apple.com \
--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