Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] 42 petabytes/day and ...
Date: Sat, 3 Feb 2024 21:11:01 +0100	[thread overview]
Message-ID: <0eb6e6dc-f9e3-400b-ba7e-695aa5ea5b6a@gmail.com> (raw)
In-Reply-To: <CAA93jw6GbkN+AbnAWzn3mmHnp_htn5uLQRZjKtYQizrp9=_y5g@mail.gmail.com>


Le 02/02/2024 à 04:07, Dave Taht via Starlink a écrit :
> from here: https://news.ycombinator.com/item?id=39200323
>
> There were two things that fell out of reading that article for me.
>
> "each laser is grossly underused on average, at 0.432% of its maximum capacity."
>
> +
>
> "Brashears also said Starlink’s laser system was able to connect two
> satellites over 5,400 kilometers (3,355 miles) apart. The link was so
> long “it cut down through the atmosphere, all the way down to 30
> kilometers above the surface of the Earth,” he said, before the
> connection broke."

It looks spectacular.

A starlink latency of say 40ms on such a long distance 5400km between 
sats seems remarkable.  Note that the corresponding on-ground distance 
between two homes served by these two sats would be smaller, perhaps 
3000km(?).

It is easy to compare that via-stalink latency to a ping RTT on a ground 
only link on comparable distance.

Alex

>
> So there IS a way to achieve previously unheard of lower latencies (at
> a cost in bitrate) across starlink across their network. Two hops to
> go 10,000km.
>
> I loved mark handley's original animation of how the ISL's were
> supposed to work, but given the orbits  here, I kind of wish it was
> easy to plug the assumptions in and figure out what the NY -> tokoyo
> run would take in terms of hops and estimated switching overhead,
> given this distance record.
>
> How much data and what kind of data would benefit from that latency
> reduction is a matter of speculation. "Buy! Sell!" between tokoyo and
> london arbitrage was one of my first speculations many years ago.
>

      parent reply	other threads:[~2024-02-03 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  3:07 Dave Taht
2024-02-02 15:37 ` Spencer Sevilla
2024-02-02 16:44   ` Mark Handley
2024-02-03 20:11 ` 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=0eb6e6dc-f9e3-400b-ba7e-695aa5ea5b6a@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