Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Daniel AJ Sokolov <daniel@falco.ca>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Optimized for Speedtest?
Date: Tue, 15 Mar 2022 17:39:06 -0500	[thread overview]
Message-ID: <CAA93jw5_oZs6m3PO6BYOWwtWmvWv1-9sez4iyjMKsB8yGwavgw@mail.gmail.com> (raw)
In-Reply-To: <08c6ab5c-6a9d-e555-671c-5c59cffcd02d@falco.ca>

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

On Tue, Mar 15, 2022 at 5:09 PM Daniel AJ Sokolov <daniel@falco.ca> wrote:
>
> Hello,
>
>  From this list I have learned that Starlink is optimized to shine in
> tests with speedtest.net and similar sites, but that transmission rates
> drop quickly after about 15 seconds.

That is not strictly true. The trend is a low rate for the initial
15s, then a boost, then variable. It happens that speedtest reports
the *last* result in the typically 20s it runs,
so by that light is starlink is "optimized for speedtest". Much of the
internet is "optimized for speedtest", tons of services basically blow
up classic tcp congestion controls at T+21s.

Attached are two example flent test runs, a rrul test from one project
member's dishy, and a tcp_nup test from anothers.

For reference also attached is how a present day WISP 60Ghz radio
functions, one which has FQ and AQM, with consistent bandwidth, and
only ~5ms latency swings. Ideally the latency on starlink would not go
over 10ms their baseline ~40ms latency, under these loads.

Comparing the later two tests you can see the inversions between
bandwidth and latency that come from the fixed length fifos starlink
uses at any of the roughly 3
speed settings we currently see.

PS - most web pages cannot use more than 25MBit in the 3s they typically take.

> How do they do that, technically?

Allocate bandwidth? Unknown. Ever 15s seems silly. Not modifying queue
length and/not using a smarter queuing algo like fq_codel or cake when
they do change the bandwidth allocation is the simple flaw in their
design I keep hoping they'll fix.

>
> Is that a result of Bufferbloat?

Yes. The rrul test is often illustrative of the problem on how slowly
the internet operates during an upload clogging up the queue, or vice
versa. Most ISPs do some sort of ack filtering or prioritization to
make uploads interfere less with downloads, or use AQM, fq or a
combination of both.

> Is that a a specific code in the modem
> to cheat, like some car manufacturers cheated on emissions tests?

I hope not. No, they do have limited capacity, do have to change sats,
do need to allocate bandwidth sanely. AND buffering.

> Is
> that something done in the satellites who shift capacity from other
> users to those users who initiate downloads? Is that done on the backhaul?

Wish we knew. In my ideal world they would supply a statistic that a
sch_cake could take and vary the rate/buffering based on that on the
home router, or just do it more right
in the dishy and head ends with cake + BQL.

>
> Thank you
> Daniel
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink



-- 
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org

Dave Täht CEO, TekLibre, LLC

[-- Attachment #2: rrul_be_-_dlangs-dishy.png --]
[-- Type: image/png, Size: 216268 bytes --]

[-- Attachment #3: 60ghzradio.png --]
[-- Type: image/png, Size: 120553 bytes --]

[-- Attachment #4: tcp_nup_-_nathan-dishy.png --]
[-- Type: image/png, Size: 151795 bytes --]

  parent reply	other threads:[~2022-03-15 22:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 22:09 Daniel AJ Sokolov
2022-03-15 22:37 ` Nathan Owens
2022-03-15 22:39 ` Dave Taht [this message]
2022-03-15 22:47   ` Nathan Owens
2022-03-15 22:51     ` Dave Taht
2022-03-15 22:53       ` Dave Taht
2022-03-15 22:57       ` Nathan Owens
2022-03-16 13:40     ` Nathan Owens
2022-03-16 13:48     ` Nathan Owens
2022-03-15 22:48   ` Dave Taht
2022-03-16  3:48     ` Dave Taht
2022-03-16  3:49       ` Dave Taht
2022-03-15 23:38   ` 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=CAA93jw5_oZs6m3PO6BYOWwtWmvWv1-9sez4iyjMKsB8yGwavgw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=daniel@falco.ca \
    --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