Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Daniel Schien <Daniel.Schien@bristol.ac.uk>
Cc: Vint Cerf <vint=40google.com@dmarc.ietf.org>,
	 "tom@evslin.com" <tom@evslin.com>,
	 starlink <starlink@lists.bufferbloat.net>,
	 "e-impact@ietf.org" <e-impact@ietf.org>
Subject: Re: [Starlink] [E-impact] DataCenters in Space (was Re: fiber IXPs in space)
Date: Wed, 26 Apr 2023 20:50:25 -0700 (PDT)	[thread overview]
Message-ID: <24775q18-p46r-916s-59o8-q1q98rr57080@ynat.uz> (raw)
In-Reply-To: <DB9PR06MB8843FFD2FF2CC041D2AE1916A4639@DB9PR06MB8843.eurprd06.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

On Thu, 20 Apr 2023, Daniel Schien via Starlink wrote:

> I assume any object in orbit will be hidden from the sun some of the time. So, the machines will require some pretty big battery to go up with them.

less than you would think, as you get further away from the earth, the shadow of 
the earth is smaller (think about a lunar eclipse, the shadow of the earth is 
barely the size of the moon, and the eclipse doesn't last very long)

> I'd like to also know what the launch cost is.

Shuttle was ~50k/Kg
pre-spacex expendable rockets were ~$10k/kg
Falcon 9 has driven costs down into the ballpark of $1k/Kg (with indications 
that SpaceX internal costs may be significantly lower, but they price their 
launches at what the market will bear, under their competitors pricing)
Starship could get this down to under $10/Kg

David Lang

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink

  parent reply	other threads:[~2023-04-27  3:50 UTC|newest]

Thread overview: 31+ 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 [this message]
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
     [not found] <mailman.128.1682362805.60209.e-impact@ietf.org>
2023-04-24 20:59 ` [Starlink] [E-impact] " Priyanka Sinha
2023-04-27  3:18   ` Eugene Chang

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=24775q18-p46r-916s-59o8-q1q98rr57080@ynat.uz \
    --to=david@lang.hm \
    --cc=Daniel.Schien@bristol.ac.uk \
    --cc=e-impact@ietf.org \
    --cc=starlink@lists.bufferbloat.net \
    --cc=tom@evslin.com \
    --cc=vint=40google.com@dmarc.ietf.org \
    /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