Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sauli Kiviranta <smksauli@gmail.com>
To: David Lang <david@lang.hm>
Cc: "David P. Reed" <dpreed@deepplum.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] some post Starship launch thoughts
Date: Thu, 11 May 2023 19:24:43 +0300	[thread overview]
Message-ID: <CAJbqEYA683_jLW2qMiCepN326dO5XjwrQzRQ3UmJq_ngV_agKQ@mail.gmail.com> (raw)
In-Reply-To: <q7666n17-r04r-3112-p635-10rs3r5n7331@ynat.uz>

Somehow this ended up in spam by gmail.

What you explained makes it even more remarkable, I would not indeed
call it being overlooked. That is just plain failure of scaling
whatever they learned from those iterations. It is definitely not
obvious, just remarkable.

Thanks for sharing these details!

Best regards,
Sauli

On 4/26/23, David Lang <david@lang.hm> wrote:
> On Wed, 26 Apr 2023, Sauli Kiviranta via Starlink wrote:
>
>> It was interesting to see that such a "basic" thing as the launch pad
>> structure was overlooked as a rather large problem vector. Even if it
>> was recognized as an issue, that it turned out to be a majestic
>> borderline catastrophic issue was surprise to me. Easy to overlook
>> everything when scaling up. There is a great book on the topic of
>> systems and their scaling parts when sizes change "Scale: The
>> Universal Laws of Growth" by Geoffrey West, highly recommended.
>
> It wasn't overlooked, they did a 7 engine static fire, it damaged the pad,
> so
> they improved it, they did a 14 engine static fire and it damaged it again,
> so
> they improved it again, they did a 31 engine 50% power static fire with
> minimal
> pad damage and had other blocks of material mounted in the engine exhaust at
>
> McGreggor. They just failed to catch some inflection point between the 50%
> power
> test and the full power test. They expected some damage to the pad, but not
>
> nearly as much as what happened.
>
> David Lang
>

  reply	other threads:[~2023-05-11 16:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.798.1682383621.1222.starlink@lists.bufferbloat.net>
2023-04-25 20:40 ` David P. Reed
2023-04-25 21:31   ` Sauli Kiviranta
2023-04-25 22:37     ` David Lang
2023-05-11 16:24       ` Sauli Kiviranta [this message]
2023-04-25 22:33   ` David Lang
2023-04-24 16:02 David Fernández
  -- strict thread matches above, loose matches on Subject: below --
2023-04-24 14:12 Dave Taht
2023-04-24 15:16 ` Michael Richardson
2023-04-24 15:27   ` Dave Taht
2023-04-24 15:37     ` Michael Richardson
2023-04-24 15:49       ` Nathan Owens
2023-04-24 19:03   ` David Lang
2023-04-24 19:16 ` David Lang
2023-04-25  0:46   ` Eugene Chang
2023-04-25  2:20     ` David Lang
2023-04-25 22:31       ` Bruce Perens
2023-04-25 23:04         ` Eugene Chang
2023-04-25 23:22           ` David Lang
2023-04-25 23:55             ` Eugene Y Chang
2023-04-26 19:14         ` Michael Richardson
2023-04-25  1:01 ` Bruce Perens
2023-04-26 19:29 ` Dave Taht
2023-04-26 20:05   ` Sebastian Moeller
2023-04-26 20:41   ` Rodney W. Grimes
2023-04-26 21:05     ` Eugene Y Chang
2023-04-26 22:15       ` Mark Handley
2023-04-26 21:10     ` Dave Taht
2023-04-26 21:26       ` Eugene Chang
2023-04-26 22:31       ` Rodney W. Grimes
2023-04-26 22:38         ` Bruce Perens
2023-04-26 23:25         ` Eugene Chang
2023-04-27  3:44         ` David Lang
2023-04-27 14:09           ` Rodney W. Grimes

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=CAJbqEYA683_jLW2qMiCepN326dO5XjwrQzRQ3UmJq_ngV_agKQ@mail.gmail.com \
    --to=smksauli@gmail.com \
    --cc=david@lang.hm \
    --cc=dpreed@deepplum.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