Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: J Pan <Pan@uvic.ca>
To: the keyboard of geoff goodfellow <geoff@iconia.com>
Cc: Starlink <Starlink@lists.bufferbloat.net>,
	"Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [Starlink] SpaceX: "IMPROVING STARLINK’S LATENCY" (via Nathan Owens)
Date: Fri, 8 Mar 2024 11:50:04 -0800	[thread overview]
Message-ID: <CAHn=e4g3wFB_KOXLY=Lt9b9DrtOxdUZZ2TzvLsJL7nHWGWD9Mg@mail.gmail.com> (raw)
In-Reply-To: <CAEf-zrimzKm+ReDLqXhwEqZ_FJCSko1-qrwn-_LmimD156Wdjg@mail.gmail.com>

they benefited a lot from this mailing list and the research and even
user community at large
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan


On Fri, Mar 8, 2024 at 11:40 AM the keyboard of geoff goodfellow via
Starlink <starlink@lists.bufferbloat.net> wrote:
>
> Super excited to be able to share some of what we have been working on over the last few months!
> EXCERPT:
>
> Starlink engineering teams have been focused on improving the performance of our network with the goal of delivering a service with stable 20 millisecond (ms) median latency and minimal packet loss.
>
> Over the past month, we have meaningfully reduced median and worst-case latency for users around the world. In the United States alone, we reduced median latency by more than 30%, from 48.5ms to 33ms during hours of peak usage. Worst-case peak hour latency (p99) has dropped by over 60%, from over 150ms to less than 65ms. Outside of the United States, we have also reduced median latency by up to 25% and worst-case latencies by up to 35%...
>
> [...]
> https://api.starlink.com/public-files/StarlinkLatency.pdf
> via
> https://twitter.com/Starlink/status/1766179308887028005
> &
> https://twitter.com/VirtuallyNathan/status/1766179789927522460
>
>
> --
> Geoff.Goodfellow@iconia.com
> living as The Truth is True
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2024-03-08 19:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 19:40 the keyboard of geoff goodfellow
2024-03-08 19:50 ` J Pan [this message]
2024-03-08 20:09   ` the keyboard of geoff goodfellow
2024-03-08 20:25     ` Frantisek Borsik
2024-03-08 20:31     ` Dave Taht
2024-03-08 23:44       ` [Starlink] When Flows Collide? Jack Haverty
2024-03-09  2:57         ` [Starlink] [NNagain] " David Lang
2024-03-09 19:08           ` Jack Haverty
2024-03-09 19:45             ` rjmcmahon
2024-03-09 20:08             ` David Lang
2024-03-10 17:41       ` [Starlink] SpaceX: "IMPROVING STARLINK’S LATENCY" (via Nathan Owens) Michael Richardson
2024-03-08 20:30   ` [Starlink] [NNagain] " rjmcmahon

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=e4g3wFB_KOXLY=Lt9b9DrtOxdUZZ2TzvLsJL7nHWGWD9Mg@mail.gmail.com' \
    --to=pan@uvic.ca \
    --cc=Starlink@lists.bufferbloat.net \
    --cc=geoff@iconia.com \
    --cc=nnagain@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