Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] 42 petabytes/day and ...
Date: Thu, 1 Feb 2024 22:07:06 -0500	[thread overview]
Message-ID: <CAA93jw6GbkN+AbnAWzn3mmHnp_htn5uLQRZjKtYQizrp9=_y5g@mail.gmail.com> (raw)

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."

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.

-- 
40 years of net history, a couple songs:
https://www.youtube.com/watch?v=D9RGX6QFm5E
Dave Täht CSO, LibreQos

             reply	other threads:[~2024-02-02  3:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  3:07 Dave Taht [this message]
2024-02-02 15:37 ` Spencer Sevilla
2024-02-02 16:44   ` Mark Handley
2024-02-03 20:11 ` 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='CAA93jw6GbkN+AbnAWzn3mmHnp_htn5uLQRZjKtYQizrp9=_y5g@mail.gmail.com' \
    --to=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