From: Dave Taht <dave.taht@gmail.com>
To: Nathan Owens <nathan@nathan.io>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] ookla's latest speedtest app does latency under load
Date: Thu, 12 May 2022 16:18:05 -0700 [thread overview]
Message-ID: <CAA93jw6z-fu9qJgOb3ZD60PEgQUXqvzpELB-LoBXi25k1LZ=yg@mail.gmail.com> (raw)
In-Reply-To: <CALjsLJutRewbZk-fqPTNJhA9WeCraB99SQtbvxFhnYGJsw1k4A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1954 bytes --]
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:
> Here's a test I did today:
> https://www.speedtest.net/my-result/i/5112435305
>
>
>
> 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
[-- Attachment #1.2: Type: text/html, Size: 3527 bytes --]
[-- Attachment #2: IMG_3074.jpg --]
[-- Type: image/jpeg, Size: 223771 bytes --]
next prev parent reply other threads:[~2022-05-12 23:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 23:04 Dave Taht
2022-05-12 23:07 ` Nathan Owens
2022-05-12 23:18 ` Dave Taht [this message]
2022-05-12 23:35 ` Brennen Smith
2022-05-13 7:58 ` Möller, Sebastian
2022-05-17 15:43 ` Luis A. Cornejo
2022-05-18 13:25 ` Livingood, Jason
2022-05-18 13:29 ` Brennen Smith
2022-06-07 11:13 ` Bjørn Ivar Teigen
2022-05-13 8:35 ` Nitinder Mohan
2022-05-13 13:47 ` Livingood, Jason
2022-05-13 14:15 ` Dave Taht
2022-05-13 14:50 ` Sebastian Moeller
2022-05-19 14:06 ` [Starlink] [EXTERNAL] " Livingood, Jason
2022-05-12 23:37 ` [Starlink] " Ricky Mok
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6z-fu9qJgOb3ZD60PEgQUXqvzpELB-LoBXi25k1LZ=yg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=nathan@nathan.io \
--cc=starlink@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