I noticed Ookla changed the measurement method in the web version as well.
They measured download throughput using two different servers
instead of one.
Ricky
Yea. peak 2500ms latency on download, 600ms on upload, that's about right. :/ The upload figure appears to be a bit lower (better) than what I measured 1 year ago, here (for the 30 or so new subscribers on this list, this was why I started it): https://docs.google.com/document/d/1puRjUVxJ6cCv-rgQ_zn-jWZU9ae0jZbFATLf4PQKblM/edit
I don't know if ookla are throwing out arp related stuff, or using the 99th percentile to calculate the final figure. I hope to learn more about their calculations in the coming weeks.
I do keep hoping we can get more updated flent data over longer intervals than 20s. With starlink changing their allocation scheme every 15s, what number do you pick?
And like I said, some packet caps of this app would be good, too.
On Thu, May 12, 2022 at 4:07 PM Nathan Owens <nathan@nathan.io> wrote:
On Thu, May 12, 2022 at 4:04 PM Dave Taht <dave.taht@gmail.com> wrote:
Ookla has just put out an ios and android app that also continuously
measures latency under load.
I'm interested in calibrating the results of that vs a vs flent
benchmarks verses starlink. Can someone here give this a shot? More
details here:
https://www.ookla.com/articles/introducing-loaded-latency
IDEALLY, this would be over wifi -> starlink , with a packet capture
in the middle. But I'd settle for a few test results from starlink
folk of this new app, first.
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
_______________________________________________ Starlink mailing list Starlink@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/starlink