General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Christoph Paasch <cpaasch@apple.com>
Cc: Rpm <rpm@lists.bufferbloat.net>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Ookla - Introducing a Better Measure of Latency
Date: Thu, 12 May 2022 22:11:33 +0200	[thread overview]
Message-ID: <E00D6D61-AAD1-466F-9B49-C37D4FE383E8@gmx.de> (raw)
In-Reply-To: <E7CFAAB6-2D53-4BEE-86E2-46E2D018723C@apple.com>

Hi Christoph,

nice! Thanks for posting.


For Android (and iOS) Ookla's speedtest app now reports a "Detailed result" page which contains:
1) Upload and download rates (albeit without information what exactly was measured) 
2) Data volume used per direction (but not the precise duration of the test)
3) Idle, download, upload responsiveness measures:
(probably) the average, the jitter, the minimum, and the maximum
4) Packet loss percentage

This is quite an improvement and achievement! I would wish for a bit more information about the details, like how was latency exactly measured, how many probes were used per direction and what are the individual delay values...

Unfortunately, the macos client seems not yet updated and the web based test also still only reports the idle RTT. I hope it is only a matter of time for those to be updated.

Regards
	Sebastian




> On May 12, 2022, at 19:15, Christoph Paasch via Bloat <bloat@lists.bufferbloat.net> wrote:
> 
> Ookla's measure of "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


  parent reply	other threads:[~2022-05-12 20:11 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
2022-05-13  7:48       ` Sebastian Moeller
2022-05-13 16:53         ` Christoph Paasch
2022-05-12 20:11 ` Sebastian Moeller [this message]
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=E00D6D61-AAD1-466F-9B49-C37D4FE383E8@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cpaasch@apple.com \
    --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