Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] 1986DA analyzed
Date: Sun, 3 Oct 2021 08:18:04 -0700	[thread overview]
Message-ID: <CAA93jw6p8SBO3v-NPu=jZ6QM_0DHS963+dFdjWNjWEcu35Tj2w@mail.gmail.com> (raw)

A huge factor in my interest in starlink - in trying to improve their
internet service - is to  help get humanity into the solar system. I'm
not a huge fan of "mars direct" and have always
felt,  a little detour, to pick up some needed materials from
off-planet, was desirable.

The upcoming psyche mission (to be flown on a falcon heavy) is pretty
exciting, see here:

https://psyche.asu.edu/mission/instruments-science-investigations/

BUT, solar electric propulsion doesn't work all that well that far in
the belt, that mission's duration is 6+ years just to get anywhere,
and I'd always felt that trying to find suitable asteroids in more
reachable orbits, particularly for "deep impact" style missions,
would reduce the cycle time from launch to data.

This paper crossed my desk this morning, discussing two NEAs (near
earth asteroids) that look to be very similar to
psyche in their metallic composition:

https://iopscience.iop.org/article/10.3847/PSJ/ac235f/pdf

The money quote (literally): "the annual value, if mined, over 50
years, was 233 billion dollars/yr".

Oddly enough, they didn't mention what the delta-v required to get to
either, was, so I looked that
up via lance benners tool, which appears to be down at the moment, or
has moved, this is via
archive.org, which lists candidates with as low as half the delta-v
required to reach the moon or mars.

https://web.archive.org/web/20210202035814/https://echo.jpl.nasa.gov/~lance/delta_v/delta_v.rendezvous.html

                                                DELTA-V (ASTEROID)/
                                           PROVISIONAL  DELTA-V    DELTA-V FOR
RANK  PERCENTILE ASTEROID NAME             DESIGNATION  (KM/S)    THE
MOON MARS   H (mag) a (AU)   e     i (deg)

9545   45.79       (6178)                   1986 DA      7.197
1.200   1.142    15.1   2.823  0.582    4.3  RADAR


2016 ED85 wasn't listed, and the delta-v required of 7.197 is sadly a
bit more than the 6.3 of mars...  usually an impact mission
is much less but I can't seem to find the right url for that.

...

It is terribly ambitious for me to not only strongly suggest that
starlink put vastly better queue management into their three main
routing systems in their next release, so to provide low latency for
all packets, not just ping, but to then also suggest they look
strongly into the possibilities of asteroid mining[1] to get them on
their way to mars... but it's a lovely sunday morning, and a good day
to dream.

I return now to fixing up my broken down motor in my boat, and
prepping to log out, and sail away.

[1] https://the-edge.blogspot.com/2012/04/for-nearly-9-years-ive-had-one-of-my.html


-- 
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw

Dave Täht CEO, TekLibre, LLC

                 reply	other threads:[~2021-10-03 15:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAA93jw6p8SBO3v-NPu=jZ6QM_0DHS963+dFdjWNjWEcu35Tj2w@mail.gmail.com' \
    --to=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