Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Data centers are racing to space — and regulation can’t keep up
Date: Fri, 27 Feb 2026 10:36:51 +1300	[thread overview]
Message-ID: <b57f34ed-7c83-4da2-a542-ee89bcf71275@auckland.ac.nz> (raw)
In-Reply-To: <VI1PR09MB2621888AE575127753C4707B8D72A@VI1PR09MB2621.eurprd09.prod.outlook.com>

On 27/02/2026 2:56 am, Nitinder Mohan via Starlink wrote:
>    1.
> The downlink bottleneck is the real motivation for space computing, not replacing ground data centers.

Now how bad is that bottleneck really when you're operating a large 
constellation, in which each satellite can downlink?

Currently, there is a significant bottleneck in terms of downlinking to 
end users with Dishys. Why?

1) You only really have the Ku band. Lower down is crowded, further up 
there's a problem with the atmosphere between your sats and the Dishy.
2) You have the need to keep end user devices cheap (read: small), which 
limits gain and phased array directionality and selectivity.

But when we're talking data centers, we're not talking downlinking to 
end users with Dishys. We're talking downlinking to other 
infrastructure. Unlike an end user, where there's no choice in terms of 
geographical location to downlink to, infrastructure is already 
geographically diverse. SpaceX have gateways all over the place in Ka 
and higher bands, so in principle they can downlink to wherever the 
weather is in their favour - which likely it is pretty much all the time 
somewhere in their empire. ISLs help the data get there.

If we go beyond classic TCP and use, say, linear network coding for 
delivery via multiple downlink paths, then this could even look elegant.

So the only issue that then remains in this respect is latency / jitter.

>   2.
> Orbital data centers serving Earth-based users face fundamental physics constraints, exactly as this thread has identified. Heat dissipation is the hardest problem. Satellites can only radiate heat, and available radiator surface area is strictly limited. Unlike ground facilities with active cooling, there is a hard thermodynamic ceiling on how much computation any individual satellite can sustain. The seminar reached strong consensus that the "data center in space" concept for general Earth-centric workloads is not validated, and the sustainability math does not currently work out.
Now that assumes conventional computation. The reason why we get all 
that heat in our computers is because their logic gates spend a lot of 
their time in no-man's land between 0 and 1 bits: 0 bits might be 
"switch open", i.e., voltage but no current, which means no power being 
dissipated, while 1 bits might mean "switch closed", with current but no 
voltage, so also no power being dissipated. But *while* they're 
switching, there's both current and voltage, and hence power being 
dissipated to the gates' environment.

Compute in ways that either reduce the time spent switching or that use 
less power (e.g., adiabatic logic) and this becomes less of an issue.

A lot of the other issues persist, though.

-- 
****************************************************************
Dr. Ulrich Speidel

School of Computer Science

Room 303S.594 (City Campus)

The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************




  reply	other threads:[~2026-02-26 21:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 14:05 [Starlink] Data centers are racing to space — and regulation can’t keep up Hesham ElBakoury
2026-02-25 14:30 ` [Starlink] " David Collier-Brown
2026-02-25 14:32   ` [Starlink] Re: Data centers are racing to space ??? and regulation can???t " Gert Doering
2026-02-25 14:42   ` [Starlink] Re: Data centers are racing to space — and regulation can’t " Hesham ElBakoury
2026-02-26  4:28     ` J Pan
     [not found]       ` <CAFvDQ9p68AFJ5cQTpyx=HkA2Cf6r1m6F3ssaJh-OJK4kqK=PDQ@mail.gmail.com>
2026-02-26  5:54         ` J Pan
2026-02-26  6:01           ` Hesham ElBakoury
2026-02-25 14:50   ` Daniel AJ Sokolov
2026-02-26  1:33     ` David Lang
2026-02-26  2:38       ` Nick Matthews
2026-02-26  4:39         ` David Lang
2026-02-26 11:54           ` Mark Handley
2026-02-26 13:36             ` Vint Cerf
2026-02-26 13:56               ` Nitinder Mohan
2026-02-26 21:36                 ` Ulrich Speidel [this message]
2026-02-26 23:02                   ` Brandon Butterworth
2026-02-26 23:16                     ` Nitinder Mohan
2026-02-26 23:44                       ` Ulrich Speidel
2026-02-27  1:01                         ` Joe Hamelin
2026-02-27  1:47                           ` David Lang
2026-02-27 14:26                             ` [Starlink] Why Data Centers In Space Won't Work [Yet] (A non-canonical list) Sascha Meinrath
2026-02-27 15:07                               ` [Starlink] " David Lang
2026-02-27 15:15                               ` Daniel AJ Sokolov
2026-02-27 15:22                                 ` Gert Doering
2026-02-26 14:14               ` [Starlink] Re: Data centers are racing to space — and regulation can’t keep up Mark Handley
2026-02-26 18:01             ` David Lang
2026-02-25 20:26   ` Brandon Butterworth
2026-02-26  1:28   ` David Lang
2026-02-26  4:49 ` David Lang

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=b57f34ed-7c83-4da2-a542-ee89bcf71275@auckland.ac.nz \
    --to=u.speidel@auckland.ac.nz \
    --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