Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink "beam spread"
Date: Wed, 31 Aug 2022 13:28:09 -0700 (PDT)	[thread overview]
Message-ID: <7q848925-o6qn-1934-n4s9-n493n9sp9op9@ynat.uz> (raw)
In-Reply-To: <1661975488.138231368@apps.rackspace.com>

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

On Wed, 31 Aug 2022, David P. Reed via Starlink wrote:

> My point is that the discussion here has focused entirely on achievable bitrate maximum, with no load and no burstiness.

well, to be fair, some of that is in response to 'just looking at the bitrate, 
starlink cannot possibly perform well' posts

> This isn't fixed by having more spatial control, to the extent that is 
> possible.

agreed, the spactial control discussion is just a response to 'it can't 
possibly...' posts

> It *is* fixable by suitable Automatic Queue Management in the 
> satellite path (which will be the "bottleneck link" between the home and the 
> public Internet), plus suitable end-to-end protocol congestion management that 
> responds to drops or ECN. (I don't know if the satellite looks at the packet 
> hard enough and has enough state to set the ECN bit or that it has enough 
> state to achieve bloom filter based fair queue dropping).

if the sats are going to have the ability to route through other satellites, 
they have to be looking at the packets, and once you start doing that, looking 
at ECN should not be a significant load.

David Lang

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2022-08-31 20:28 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.800.1661972667.1281.starlink@lists.bufferbloat.net>
2022-08-31 19:51 ` David P. Reed
2022-08-31 20:28   ` David Lang [this message]
2022-08-31 21:17     ` David P. Reed
2022-08-31 21:33       ` David Lang
2022-09-01  7:05         ` Mike Puchol
2022-09-01 11:43           ` Ulrich Speidel
2022-09-01  8:09       ` David Lang
2022-08-31 20:24 ` [Starlink] CDNs in space! David P. Reed
2022-08-31 21:09   ` Mike Puchol
2022-08-31 22:19   ` Radostin Stoyanov
2022-08-31 22:46   ` Ulrich Speidel
2022-09-01  9:57   ` Brandon Butterworth
2022-09-01 15:19 [Starlink] Starlink "beam spread" David Fernández
2022-09-01 16:33 ` Darrell Budic
2022-09-02  9:32   ` David Fernández
2022-09-01 19:56 ` Michael Richardson
2022-09-02 12:27   ` Sebastian Moeller
2022-09-02 18:34     ` Michael Richardson
2022-09-02 20:11       ` Sebastian Moeller
  -- strict thread matches above, loose matches on Subject: below --
2022-08-31 14:51 David Fernández
2022-08-31 18:09 ` Michael Richardson
2022-08-31 21:46 ` Ulrich Speidel
2022-08-31 23:44   ` Lin Han
2022-09-01 19:26   ` Dave Taht
2022-08-31  8:15 David Fernández
     [not found] <mailman.3.1661875202.32670.starlink@lists.bufferbloat.net>
2022-08-30 16:53 ` David P. Reed
2022-08-30 17:32   ` Doc Searls
2022-08-30 20:09     ` Mike Puchol
2022-08-30 20:35       ` Daniel AJ Sokolov
2022-08-30 20:40         ` Mike Puchol
2022-08-30 21:09       ` David Lang
2022-08-30 21:01   ` David Lang
2022-08-30 22:07     ` Brandon Butterworth
2022-08-30 22:21       ` David Lang
2022-08-30 22:37         ` Brandon Butterworth
2022-08-30 23:07           ` David Lang
2022-08-30 23:45             ` Brandon Butterworth
2022-08-30 23:28           ` David P. Reed
2022-08-31  0:12             ` David Lang
2022-08-31  0:31               ` Dave Taht
2022-08-31  0:32               ` David P. Reed
2022-08-31 10:29                 ` Dave Collier-Brown
2022-08-31 18:51                   ` David Lang
2022-08-31 19:04             ` Dave Taht
2022-08-30 22:50       ` Ulrich Speidel
2022-08-30 23:13         ` David Lang
2022-08-31  0:46         ` tom
2022-08-31  0:58           ` Dave Taht
2022-08-31  7:36             ` Mike Puchol
2022-08-31  6:26         ` Sebastian Moeller
2022-08-31  7:25           ` Ulrich Speidel
2022-08-31  7:31             ` Hayden Simon
2022-08-31  7:33             ` David Lang
2022-08-31  9:59               ` Mike Puchol
2022-08-31 10:06                 ` David Lang
2022-08-31 10:12                   ` Mike Puchol
2022-08-31 17:52                 ` Dick Roy
2022-08-31 13:41               ` Ulrich Speidel
2022-08-31 14:30                 ` Mike Puchol
2022-08-31 21:44                   ` Ulrich Speidel
2022-09-01  7:58                 ` Sebastian Moeller
2022-09-01 11:38                   ` Ulrich Speidel
2022-09-01 19:54                     ` Michael Richardson
2022-09-01 21:08                       ` tom
2022-09-02  7:52                         ` Sebastian Moeller
2022-09-02 12:29                           ` tom
2022-08-31  7:49             ` Sebastian Moeller
2022-08-31  9:25               ` Brandon Butterworth
2022-08-31  9:34                 ` David Lang
2022-09-01  9:12                   ` Brandon Butterworth
2022-08-31 14:52   ` Dave Taht

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=7q848925-o6qn-1934-n4s9-n493n9sp9op9@ynat.uz \
    --to=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