Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: J Pan <Pan@uvic.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] musk: 28ms median latency on starlink
Date: Mon, 3 Jun 2024 17:08:48 -0700	[thread overview]
Message-ID: <CAHn=e4jiyhbxg+6kp_SU33y3OhumGyEfQ2Xoen7V39jqjvoL1Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5V0JTEgTyn4iuXfrHLNxnKyWDWeZKj_Ao=8OCY_R4fYg@mail.gmail.com>

it's better if elon can show the distribution of the ut-pop latency,
as median (or p50) does not tell anything about p99 as shown in
https://api.starlink.com/public-files/StarlinkLatency.pdf
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan

On Sun, Jun 2, 2024 at 10:13 AM Dave Taht via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> 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
>
> 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
>
> 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 Waves Podcast
> Dave Täht CSO, LibreQos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

  parent reply	other threads:[~2024-06-04  0:09 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 [this message]
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

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='CAHn=e4jiyhbxg+6kp_SU33y3OhumGyEfQ2Xoen7V39jqjvoL1Q@mail.gmail.com' \
    --to=pan@uvic.ca \
    --cc=dave.taht@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