Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Rodney W. Grimes" <starlink@gndrsh.dnsmgr.net>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] some post Starship launch thoughts
Date: Wed, 26 Apr 2023 14:10:51 -0700	[thread overview]
Message-ID: <CAA93jw7STDL_Z7kAVSQ+kXu91A_V_yOLQS-OQL8i4262sHOHSw@mail.gmail.com> (raw)
In-Reply-To: <202304262041.33QKfOVh096953@gndrsh.dnsmgr.net>

On Wed, Apr 26, 2023 at 1:41 PM Rodney W. Grimes
<starlink@gndrsh.dnsmgr.net> wrote:
>
> > As always I enjoy the flood of information we get on this list!
> >
> > still, so far, my research on a nitrogen deluge system (instead of
> > water) has come up empty for me, except as a fire suppressant. So it?s
> > either crazy or brilliant. Or both! I really liked the idea of
> > something cooler that was a natural byproduct of the LOX process...
>
> I dont think cooler does much, isnt it the "energy of vaporization"
> that is actually doing all the "work" in this type of system?
>
> H2O is 40.7 kJ/mol and LN2 is 5.6 kJ/mol so you would
> need ~7 times as much LN2 to do the same work.

Now that! was the kind of numbers I was looking for!

Still, water has to come from somewhere, and be stored. I will keep
thinking about it. I like that they seem to think that a water cooled
steel plate will suffice.

> And the reason N2 is used as a fire suppressant is again not
> because of temperature, but because it displaces the O2 and
> suffocates the fire.  N2 is also easier on our ozone layer
> than the prior used Halon.  Finally, this is usually
> compressed N2 gas, not LN2.
>
> --
> Rod Grimes                                                 rgrimes@freebsd.org


--
AMA March 31: https://www.broadband.io/c/broadband-grant-events/dave-taht
Dave Täht CEO, TekLibre, LLC

  parent reply	other threads:[~2023-04-26 21:11 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 22:29         ` [Starlink] Fondag Bruce Perens
2023-04-26 22:32           ` Rodney W. Grimes
2023-04-26 22:35           ` Nathan Owens
2023-04-26 23:09             ` Nathan Owens
2023-04-27  3:42             ` David Lang
2023-04-26 21:10     ` Dave Taht [this message]
2023-04-26 21:26       ` [Starlink] some post Starship launch thoughts 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
2023-04-24 16:02 David Fernández
     [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
2023-04-25 22:33   ` 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=CAA93jw7STDL_Z7kAVSQ+kXu91A_V_yOLQS-OQL8i4262sHOHSw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=starlink@gndrsh.dnsmgr.net \
    --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