Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Darrell Budic <budic@onholyground.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink tidbits from NANOG
Date: Thu, 4 Nov 2021 20:46:08 -0500	[thread overview]
Message-ID: <89E6EE2E-CEDC-4150-B68F-CC66727E7C48@onholyground.com> (raw)
In-Reply-To: <CAA93jw6hDodGpCA_hfzH7abk+jAXtnsQ+GR0=r4RO5CJ8H3vgg@mail.gmail.com>



> On Nov 4, 2021, at 11:46 AM, Dave Taht <dave.taht@gmail.com> wrote:
>> - new dishes are in the works, v4 coming with lower power use, more capacity, not round any more
>> - larger dishes coming for commercial apps
> 
>> - as we know, they aren’t doing any AQM yet, but it sounds like it may be in the works and we may see it in new code in 4-6 months. Not my guys department, so no more details.
> 
> fq is a better start.
> 
> Just someone telling me under pain of death, "dave, you can't talk for
> X months, but we're going to do cake/fq-codel/pie/something" would be
> comforting. There's a whole internet elsewhere left to fix, starlink
> getting it right and a little publicity around it would do wonders...
> and certainly wifi is highest on my list. As it is, I got annoyed
> enough last week to try and get the autorate sensing code to work well
> on starlink. There's a prototype now that seems to be working well on
> lte, see here: https://forum.openwrt.org/t/cakes-autorate-ingress-testing-needed/108848/186

Forgot to say that I did pitch the advantages of lowering latency and jumping over many other terrestrial providers for congestion control. My guy was ground networking though, but I can hope it will get passed over. Hoping I can stay in touch with them and continue to pipe things in and out of their black box...

  parent reply	other threads:[~2021-11-05  1:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 15:26 Darrell Budic
2021-11-04 16:21 ` Dave Taht
2021-11-04 16:46 ` Dave Taht
2021-11-04 17:11   ` Dave Taht
2021-11-05  1:30     ` Darrell Budic
2021-11-05  1:41   ` Darrell Budic
2021-11-05  1:46   ` Darrell Budic [this message]
2021-11-04 18:16 ` Michael Richardson
2021-11-04 18:25   ` Inemesit Affia
2021-11-04 18:29   ` Dave Taht
2021-11-04 19:10     ` Michael Richardson
2021-11-05  0:34 ` Ulrich Speidel
2021-11-05  1:05   ` Nathan Owens
2021-11-05  1:18     ` Darrell Budic
2021-11-05 22:24       ` Ulrich Speidel
2021-11-05 15:00     ` [Starlink] data sovereignty Michael Richardson
2021-11-05 15:07       ` Spencer Sevilla
2021-11-05 17:36       ` Daniel AJ Sokolov
2021-11-05 18:01       ` Daniel AJ Sokolov
2021-11-05 22:12     ` [Starlink] Starlink tidbits from NANOG Ulrich Speidel
2021-11-05  1:27   ` Darrell Budic
2021-11-05 15:03     ` Michael Richardson

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=89E6EE2E-CEDC-4150-B68F-CC66727E7C48@onholyground.com \
    --to=budic@onholyground.com \
    --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