Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] musk: 28ms median latency on starlink
Date: Wed, 5 Jun 2024 13:08:42 +0200	[thread overview]
Message-ID: <688560aa-bd7c-441d-8fde-da287b50f59c@gmail.com> (raw)
In-Reply-To: <BEA4C698-10C8-4A73-80B8-631C75DC2C3E@comcast.com>

[-- Attachment #1: Type: text/plain, Size: 4417 bytes --]


Le 04/06/2024 à 18:33, Livingood, Jason via Starlink a écrit :
>
> First question is what was the test destination? From the CPE to a 
> ground station or to something at a peering point or on the internet? 
> I would assume either to ground station or 1 hop beyond (peering 
> point)… That way we can do apples-to-apples comparisons, so to speak.
>
> In any case, there is a lot of good 3^rd party data out there for 
> this. First is RIPE Atlas. I helped get a lot of probes deployed in 
> the US and there are now 78 probes connected globally (roughly 30 
> would be sufficient to call it statistically significant): 
> https://atlas.ripe.net/probes/public?sort=-id&toggle=all&page_size=100&search=AS14593&page=1&status=1 
> <https://atlas.ripe.net/probes/public?sort=-id&toggle=all&page_size=100&search=AS14593&page=1&status=1>. 
> So if you know how to pull data from Atlas, it is there for you to 
> analyze… (see https://atlas.ripe.net/docs/apis/rest-api-manual/ and 
> https://atlas.ripe.net/docs/tools-and-code/latencymon.html
>
> There is also this recent report that used a hardware probe connected 
> over ethernet: 
> https://www.netforecast.com/wp-content/uploads/FixedWireless_LEO_CableComparisonReport_NFR5148-1.pdf
>
> Another approach similar to accessing RIPE Atlas data would be to get 
> the Cloudflare AIM data from M-Lab – see 
> https://www.measurementlab.net/blog/cloudflare-aimscoredata-announcement/. 
> There was also a recent 3^rd party report on that (see Figure 1): 
> https://www.netforecast.com/wp-content/uploads/NFR5150_NetForecast-ISP-Performance-Report-2024.pdf. 
>
>
I was having the same question of where are the test destinations when 
talking about 28ms latencies.

For my part, when I read latency evaluations expressed in milliseconds 
of RTT (round-trip time) I kind of assume we talk about using the tool 
of the website speedtest.net.  It is a very approximate number but I 
think it is understood by many people. That speedtest.net website has 
some server participants.  The test indicates where is situated the 
particular server in use.

Of course, ideally, spacex should tell precisely how they obtained that 
latency number (28ms), but I doubt they'll ever get into that kind of 
detail.  It's as if I asked them to tell what algorithm is behind xai, 
or so.

Alex

> Jason
>
> *From: *Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of 
> Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> *Reply-To: *Dave Taht <dave.taht@gmail.com>
> *Date: *Sunday, June 2, 2024 at 13:13
> *To: *Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> *Subject: *[Starlink] musk: 28ms median latency on starlink
>
> Via elon musk:
>
> Starlink just achieved a new internal median latency record of 28ms 
> yesterday! Great work by the engineering and operations teams.
>
> - https://twitter.com/elonmusk/status/1797282250574184587 
> <https://urldefense.com/v3/__https:/twitter.com/elonmusk/status/1797282250574184587__;!!CQl3mcHX2A!Fo8uFKdmFfKjawQrmiHSiyPIfMeLkSmEDbZ7r3K6SUa6razTwsaV2N4vFYYuMFizfHJf-oPpQLsMuW6fdCXIyWT4k75JoVsfRQ$>
>
> I of course, am very interested in y'all´s external measurements of 
> how well starlink is doing. For me, it is fantastic - 30Mbit uploads 
> nowadays, 0
>
> latency on the upload (how?) 
> https://www.waveform.com/tools/bufferbloat?test-id=2a1d139b-87cb-4ba4-a829-e2167801cffe 
> <https://urldefense.com/v3/__https:/www.waveform.com/tools/bufferbloat?test-id=2a1d139b-87cb-4ba4-a829-e2167801cffe__;!!CQl3mcHX2A!Fo8uFKdmFfKjawQrmiHSiyPIfMeLkSmEDbZ7r3K6SUa6razTwsaV2N4vFYYuMFizfHJf-oPpQLsMuW6fdCXIyWT4k75XAxHvIw$>
>
> I also keep hoping that the rest of the ISP industry is now paying 
> attention and deploying stuff like fq_codel and cake and libreqos, 
> but, ah well - I will settle for starlink blowing past a lot of dsl 
> and cable and finding ways to get their density up.
>
> Anyone going to the Starship launch on the 6th?
>
>
> -- 
>
> https://www.youtube.com/watch?v=BVFWSyMp3xg&t=1098s 
> <https://urldefense.com/v3/__https:/www.youtube.com/watch?v=BVFWSyMp3xg&t=1098s__;!!CQl3mcHX2A!Fo8uFKdmFfKjawQrmiHSiyPIfMeLkSmEDbZ7r3K6SUa6razTwsaV2N4vFYYuMFizfHJf-oPpQLsMuW6fdCXIyWT4k760_tKaJA$> 
> Waves Podcast
>
> Dave Täht CSO, LibreQos
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

[-- Attachment #2: Type: text/html, Size: 11538 bytes --]

      parent reply	other threads:[~2024-06-05 11:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02 17:13 Dave Taht
2024-06-02 18:17 ` Sauli Kiviranta
2024-06-02 18:23   ` Oleg Kutkov
2024-06-03 10:40 ` Ulrich Speidel
2024-06-03 16:43   ` David Lang
2024-06-03 17:41     ` Mike Puchol
2024-06-03 21:59       ` Ulrich Speidel
2024-06-04  0:08 ` J Pan
2024-06-04 14:53 ` Alexandre Petrescu
2024-06-04 18:24   ` David Lang
2024-06-04 16:33 ` Livingood, Jason
2024-06-04 18:34   ` J Pan
2024-06-05 11:08   ` Alexandre Petrescu [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/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=688560aa-bd7c-441d-8fde-da287b50f59c@gmail.com \
    --to=alexandre.petrescu@gmail.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