From: Taraldsen Erik <erik.taraldsen@telenor.no>
To: "Sebastian Moeller" <moeller0@gmx.de>, "Dave Täht" <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Rpm] Open Loaded latency data from ookla
Date: Fri, 3 Mar 2023 11:58:59 +0000 [thread overview]
Message-ID: <B92FC931-5968-4B23-A9E5-EDACF6E52985@telenor.no> (raw)
In-Reply-To: <5B1860D6-590C-4FD2-B46C-566EF06D7134@gmx.de>
Considering how much the C level management weights the level us ISP's ranks in Ooklas test - weaknesses and all, this is very good news. At least here in Norway the ranking in Ookla is used in marketing and is considered very important. If ISPs (such as Telenor who I work for) starts to slip in the rating due to bad latency numbers - we may finally get some traction to improve the situation.
-Erik
On 24/02/2023, 08:43, "Bloat on behalf of Sebastian Moeller via Bloat" <bloat-bounces@lists.bufferbloat.net <mailto:bloat-bounces@lists.bufferbloat.net> on behalf of bloat@lists.bufferbloat.net <mailto:bloat@lists.bufferbloat.net>> wrote:
Hi All,
We are getting there...
'The average latency of all tests performed in the tile, represented in milliseconds'
This is infinitely better than no under-load numbers. However, the latency distribution is neither 'normal'* nor fully symmetric (it can not, there is a hard minimum, the minimal path RTT and a hard maximum (icmp timeout) even though the distribution will likely be closer to the minimum than the maximum)**.
Next improvement possibility: they report averages and number of tests, but no measure of variance...
To put a positive spin on it, reporting luli numbers at all is great, as is the potential to improve the reporting quality with small additions!
Regards
Sebastian
*) Which is not a showstopper per se as long as the distribution is unimodal and not too skewed then the average is still intuitively interpretable, but is it?
**) My gut feeling is a beta distribution could be fitted to the data and that functions control parameters reported to better model the expected distribution shape.
P.S.: This time without links to test what triggers getting blocked...
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net <mailto:Bloat@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/bloat <https://lists.bufferbloat.net/listinfo/bloat>
prev parent reply other threads:[~2023-03-03 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 21:58 [Bloat] " Dave Taht
2023-02-24 7:43 ` [Bloat] [Rpm] " Sebastian Moeller
2023-03-03 11:58 ` Taraldsen Erik [this message]
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=B92FC931-5968-4B23-A9E5-EDACF6E52985@telenor.no \
--to=erik.taraldsen@telenor.no \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=moeller0@gmx.de \
/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