Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: J Pan <Pan@uvic.ca>
To: Gert Doering <gert@space.net>
Cc: Hesham ElBakoury <helbakoury@gmail.com>,
	5grm-satellite@ieee.org,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: How Starcloud Is Bringing Data Centers to Outer Space | NVIDIA Blog
Date: Wed, 19 Nov 2025 08:58:59 -0800	[thread overview]
Message-ID: <CAHn=e4gs=kH_3hRg1ZbBzRg78ZXC-6NuoP_Q8U4YvMDXmtua7g@mail.gmail.com> (raw)
In-Reply-To: <aR3ziVeUxbQrzAm8@Space.Net>

yes, that's why "might" ;-) and according to starcloud's
visualization, their solar panel (and heat dissipation on the other
side) is huge. whether it is feasible or sustainable, another story
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan

On Wed, Nov 19, 2025 at 8:42 AM Gert Doering <gert@space.net> wrote:
>
> hi,
>
> On Wed, Nov 19, 2025 at 08:09:48AM -0800, J Pan via Starlink wrote:
> > not physical space, but energy harvesting and heat dissipating might
> > be more favorable in space. space itself can generate enough data to
> > be cranked there, instead of beaming down
>
> Physics suggest "heat dissipation is extremely hard in vacuum".
>
> Energy harvesting on the scales that these AI DCs need is also not
> exactly trivial - under ideal conditions a square m will see something
> like 1.3kW of influx energy.  So for people talking about "gigawatts"
> of DC power, you'd need a square kilometer of solar collector, with
> good efficiency...
>
> Gert Doering
>         -- NetMaster
> --
> have you enabled IPv6 on something today...?
>
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard,
>                                            Karin Schuler, Sebastian Cler
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

  reply	other threads:[~2025-11-19 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 15:52 [Starlink] " Hesham ElBakoury
2025-11-19 16:09 ` [Starlink] " J Pan
2025-11-19 16:34   ` Hesham ElBakoury
2025-11-19 16:54     ` J Pan
2025-11-19 16:41   ` Kenneth Porter
2025-11-19 16:42   ` Gert Doering
2025-11-19 16:58     ` J Pan [this message]
2025-11-19 18:18   ` Sebastian Moeller
2025-11-20  2:47     ` David Lang
     [not found]   ` <830.1763590830@obiwan.sandelman.ca>
2025-11-20  4:33     ` J Pan
     [not found] <176362217876.1303.16872643449823923048@gauss>
2025-11-20 11:10 ` David Fernández

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=e4gs=kH_3hRg1ZbBzRg78ZXC-6NuoP_Q8U4YvMDXmtua7g@mail.gmail.com' \
    --to=pan@uvic.ca \
    --cc=5grm-satellite@ieee.org \
    --cc=gert@space.net \
    --cc=helbakoury@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