From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 'starlink' <starlink@lists.bufferbloat.net>,
"e-impact@ietf.org" <e-impact@ietf.org>
Subject: Re: [Starlink] DataCenters in Space (was Re: fiber IXPs in space)
Date: Thu, 20 Apr 2023 10:12:48 -0400 [thread overview]
Message-ID: <13368.1681999968@localhost> (raw)
In-Reply-To: <SY4PR01MB697983BB5DEB1B2AA0B2690BCE639@SY4PR01MB6979.ausprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]
Ulrich Speidel <u.speidel@auckland.ac.nz> wrote:
> Where do I even start? The lack of substantial bandwidth between space
> and ground? The extra latency between ground and space compared to
> terrestrial cloud, especially as terrestrial cloud edge can move much
> closer to customers when space can't? The fact that every LEO satellite
> is both a few 100 km from every customer and out of the customer's
> range depending on when you look? That low temperatures in space don't
> mean superconductive chips that produce zero heat, and that that heat
> is difficult to get rid of in space? That generating power in space is
> orders of magnitude more expensive than on the ground?
Oh, yeah, you are totally right on all of these points.
* Not all DC processing is user-facing though!
* Some are just pure compute loads.
* Some of the customers for these DCs might be in space in the future.
> Just because Starlink can provide a service somewhere between DSL and
> low to medium grade fibre to a few million around the globe it's not
> "done". Even with 10x the number of satellites and a couple of times
> the current capacity per satellite, Starlink isn't going to supply more
> than a couple of 100 million at best, and that's not even accounting
> for growth in demand from IOT...
Agreed.
I think that the useful/interesting result of this effort will be a
peer-reviewed model with some parameters that can be plugged into.
At 2025 prices, space-DC might not be useful.
Perhaps at 2035 prices, the balance might change.
--
Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]
prev parent reply other threads:[~2023-04-20 14:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 16:34 [Starlink] fiber IXPs in space David Fernández
2023-04-13 17:22 ` Michael Richardson
2023-04-13 18:54 ` David Fernández
2023-04-13 20:01 ` Michael Richardson
2023-04-13 20:06 ` Tom Evslin
2023-04-19 23:34 ` [Starlink] DataCenters in Space (was Re: fiber IXPs in space) Michael Richardson
2023-04-20 1:12 ` tom
2023-04-20 1:16 ` Vint Cerf
[not found] ` <ZECsG+Ldro3V5+/4@faui48e.informatik.uni-erlangen.de>
2023-04-20 3:25 ` [Starlink] [E-impact] " Hesham ElBakoury
2023-04-20 5:43 ` Daniel Schien
2023-04-20 9:31 ` Chris Adams
2023-04-20 12:50 ` Hesham ElBakoury
2023-04-20 12:51 ` Hesham ElBakoury
2023-04-27 3:13 ` Eugene Y Chang
2023-04-20 11:10 ` Hesham ElBakoury
2023-04-20 11:23 ` Sebastian Moeller
2023-04-20 11:24 ` David Lang
2023-04-20 12:06 ` Dave Collier-Brown
2023-04-20 21:21 ` Ulrich Speidel
2023-04-20 12:14 ` tom
2023-04-20 14:36 ` Rodney W. Grimes
2023-04-20 14:18 ` Michael Richardson
2023-04-27 3:50 ` David Lang
2023-04-20 11:25 ` [Starlink] " Hesham ElBakoury
2023-04-20 11:27 ` Nathan Owens
2023-04-20 11:34 ` Mike Puchol
2023-04-20 14:21 ` Michael Richardson
2023-04-20 4:33 ` Ulrich Speidel
2023-04-20 14:12 ` Michael Richardson [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=13368.1681999968@localhost \
--to=mcr+ietf@sandelman.ca \
--cc=e-impact@ietf.org \
--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