Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starship's 4th flight test was magnificent
Date: Sun, 9 Jun 2024 19:38:10 -0700 (PDT)	[thread overview]
Message-ID: <qn3ro633-q7n7-1oq4-5295-s01on981ss5s@ynat.uz> (raw)
In-Reply-To: <CAA93jw6A4TNBL5zBFsrJwi3AOjbjun2B98fjyAc3NY0BJsLUPA@mail.gmail.com>

Dave Taht wrote:

> But that left questions for me. How much overweight are Starship and the
> booster now? How much payload can they actually push to an orbit suitable
> for deploying starlink? When will they attempt payloads?

According to Elon a couple months ago, the current flying versions could deliver 
~50t to orbit (in reusable mode), they have 3 more block 1 ships left, and the 
block 2 ships will be well over 100t (not counting any benefits from weight 
reduction as they fly them more and can examine them post-recovery)

note that if they flew them in expendable mode, they could at least double that 
payload.

Block 3 ships are a bit further out, they are expecting them to handle 200t in 
fully recoverable mode.

> The second set of questions are that the newer, larger Starlink satellites
> were designed, oh, 4 years ago? with about 4x the capacity of the existing
> ones, and I imagine (and hope) that they have been continually redesigned
> with an eye to latency now, as well as capacity.

the V2 were about 8-10x the capacity of the V1.5 (the ones they could launch 
50-60 per flight), the v2 mini they have been launching (~22/flight) are about 
midway between the two. No recent word on the V2s, but Tim Dodd did another 
starbase visit with Elon before the flight, so watch for that to show up soon.

David Lang

  parent reply	other threads:[~2024-06-10  2:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 23:50 Dave Taht
2024-06-10  0:15 ` Ulrich Speidel
2024-06-10  2:22 ` Michael Richardson
2024-06-10 10:51   ` Ulrich Speidel
2024-06-10 12:04     ` David Lang
2024-06-10 12:15       ` Ulrich Speidel
2024-06-10  2:38 ` David Lang [this message]
2024-06-10 11:04   ` Ulrich Speidel
2024-06-10 12:06     ` David Lang
2024-06-10 12:21       ` Ulrich Speidel
2024-06-10  8:57 ` Alexandre Petrescu
2024-06-10  9:49   ` David Lang
2024-06-10 13:22     ` Alexandre Petrescu
2024-06-10 13:37       ` 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=qn3ro633-q7n7-1oq4-5295-s01on981ss5s@ynat.uz \
    --to=david@lang.hm \
    --cc=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