From: Brennen Smith <brennen@ookla.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] ookla's latest speedtest app does latency under load
Date: Wed, 18 May 2022 06:29:52 -0700 [thread overview]
Message-ID: <CAFwpvt4F+_GGtGsNYUc7jM5s+v-9ySruM_+9btkGZ1Yz+zzn3A@mail.gmail.com> (raw)
In-Reply-To: <99E283F8-8BCE-471A-BFBD-2106D6DCDA4D@cable.comcast.com>
[-- Attachment #1.1: Type: text/plain, Size: 8370 bytes --]
Don’t worry - result pages are in progress 👍
On Wed, May 18, 2022 at 06:26 Livingood, Jason <Jason_Livingood@comcast.com>
wrote:
> Brennan – It’d also be nice to be able to visit
> https://www.speedtest.net/result/i/5118600624 and expand/see the working
> latency numbers that Luis has below in his results image. 😊
>
>
>
> Jason
>
>
>
> *From: *Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of
> "Luis A. Cornejo" <luis.a.cornejo@gmail.com>
> *Date: *Tuesday, May 17, 2022 at 11:43
> *To: *"Möller, Sebastian" <SMoeller@dpz.eu>
> *Cc: *"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>,
> Brennen Smith <brennen@ookla.com>
> *Subject: *Re: [Starlink] ookla's latest speedtest app does latency under
> load
>
>
>
> Square dishy. North of Houston, speeds have been subpar recently compared
> to initial setup in late March (100+/10+). My cell is probably saturated
> considering my latitude, bird density, and possibly base station.
>
>
>
> https://www.speedtest.net/my-result/i/5118600624
> <https://urldefense.com/v3/__https:/www.speedtest.net/my-result/i/5118600624__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQYmOWd0Q$>
>
>
>
>
>
>
>
> On Fri, May 13, 2022 at 2:09 PM Möller, Sebastian <SMoeller@dpz.eu> wrote:
>
> Hi Brennan,
>
>
>
> really cool stuff!
>
>
>
>
> On May 13, 2022, at 01:35, Brennen Smith <brennen@ookla.com> wrote:
>
> Hey all,
>
> Here's some details about the final figures:
>
> 1. Loaded latency is simply an extension of the latency stage - same
> methodology and medium
>
>
>
> Where could I find a technical description of that method?
>
>
>
> 2. We use a "warmed up" TCP connection for latency
>
>
>
> Is that one of the load bearing flows or a non load bearing parallel flow
> that has successfully finished the TCP handshake?
>
>
>
> 3. We use the interquartile mean for the "displayed value"
>
>
>
> I wonder whether reporting something like a 95 or 99% quantiles (so either
> 1& and 99%, or 5% and 95%) in addition to min and max and interquartile
> mean would be possible? And since you use the 25 and 75% values already,
> maybe these as well?
>
>
>
> Awesome seeing those numbers in the wild and looking forward to bringing
> more awareness to this issue.
>
>
>
> For sure, so far many discussions about debugging/reducing bufferbloat
> started with people wanting to use the ubiquitious speedtest.nat nodes
> (where finding a close by one typically is easy/possible); and now this
> will actually work (assuming they use Android or iOS clients).
>
>
>
> Question: will the apps for the other OSs as well as the CLI and the web
> version also be changed to include these numbers in the foreseeable future?
>
>
>
>
>
> Kind Regards
>
> Sebastian
>
>
>
>
>
>
> Cheers,
>
> Brennen Smith
>
>
> VP Technology
>
> (206) 739-0807 | brennen@ookla.com
> linkedin.com/in/brennensmith
> <https://urldefense.com/v3/__http:/linkedin.com/in/brennensmith__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQ34tQA8k$>
>
>
> On Thu, May 12, 2022 at 4:18 PM Dave Taht <dave.taht@gmail.com> wrote:
> 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
> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1puRjUVxJ6cCv-rgQ_zn-jWZU9ae0jZbFATLf4PQKblM/edit__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQ2nOLusM$>
>
> 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
> <https://urldefense.com/v3/__https:/www.speedtest.net/my-result/i/5112435305__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQCvQ4gHo$>
>
>
>
>
>
> 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
> <https://urldefense.com/v3/__https:/www.ookla.com/articles/introducing-loaded-latency__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQtzzxpG8$>
>
> 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/
> <https://urldefense.com/v3/__https:/blog.cerowrt.org/post/state_of_fq_codel/__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQK32Qzo4$>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
> <https://urldefense.com/v3/__https:/lists.bufferbloat.net/listinfo/starlink__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQt5PBt6o$>
>
>
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> <https://urldefense.com/v3/__https:/blog.cerowrt.org/post/state_of_fq_codel/__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQK32Qzo4$>
> Dave Täht CEO, TekLibre, LLC
>
>
> This email, its contents and attachments contain information from Ziff
> Davis, Inc. and/or its affiliates which may be privileged, confidential or
> otherwise protected from disclosure. The information is intended to be for
> the addressee(s) only. If you are not an addressee, any disclosure, copy,
> distribution or use of the contents of this message is prohibited. If you
> have received this email in error, please notify the sender by reply email
> and delete the original message and any copies.
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
> <https://urldefense.com/v3/__https:/lists.bufferbloat.net/listinfo/starlink__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQt5PBt6o$>
>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
> <https://urldefense.com/v3/__https:/lists.bufferbloat.net/listinfo/starlink__;!!CQl3mcHX2A!ClDU9i5pldSBSrF1P2XIBsAEW10bCIDyoWP37dbqvXLqw_6ldzK4fq4pP1OyFSQoStkfmeGLAqrLqS6OEDgsDTJQt5PBt6o$>
>
> --
Brennen Smith VP Technology
(206) 739-0807 | brennen@ookla.com
linkedin.com/in/brennensmith <https://www.linkedin.com/in/brennensmith/>
--
This email, its contents and attachments contain information from Ziff
Davis, Inc. and/or its affiliates which may be privileged, confidential or
otherwise protected from disclosure. The information is intended to be for
the addressee(s) only. If you are not an addressee, any disclosure, copy,
distribution or use of the contents of this message is prohibited. If you
have received this email in error, please notify the sender by reply email
and delete the original message and any copies.
[-- Attachment #1.2: Type: text/html, Size: 15124 bytes --]
[-- Attachment #2: image001.jpg --]
[-- Type: image/jpeg, Size: 188465 bytes --]
[-- Attachment #3: image002.jpg --]
[-- Type: image/jpeg, Size: 82379 bytes --]
next prev parent reply other threads:[~2022-05-18 13:30 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
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 [this message]
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=CAFwpvt4F+_GGtGsNYUc7jM5s+v-9ySruM_+9btkGZ1Yz+zzn3A@mail.gmail.com \
--to=brennen@ookla.com \
--cc=Jason_Livingood@comcast.com \
--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