Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: David Lang <david@lang.hm>,
	Ulrich Speidel via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink "beam spread"
Date: Thu, 1 Sep 2022 09:58:16 +0200	[thread overview]
Message-ID: <63B8B233-DF84-4D60-884F-8A83B3ED7607@gmx.de> (raw)
In-Reply-To: <56e56b0f-07bd-fe0c-9434-2663ae9d4404@auckland.ac.nz>

Hi Ulrich,

focussing on the CDN part

> On Aug 31, 2022, at 15:41, Ulrich Speidel <u.speidel@auckland.ac.nz> wrote:
> [...]
> CDNs & Co - are NOT just dumb economic optimisations to lower bit miles. They actually improve performance, and significantly so. A lower RTT between you and a server that you grab data from via TCP allows a much faster opening of the congestion window. With initial TCP cwnd's being typically 10 packets or around 15 kB of data, having a server within 10 ms of your client means that you've transferred 15 kB after 5 ms, 45 kB after 10 ms, 105 kB after 15 ms, 225 kB after 20 ms, and 465 kB after 25 ms. Make your RTT 100 ms, and it takes half a second to get to your 465 kB. Having a CDN server in close topological proximity also generally reduces the number of queues between you and the server at which packets can die an untimely early death, and generally, by taking load off such links, reduces the probability of this happening at a lot of queues. Bottom line: Having a CDN keeps your users happier. Also, live streaming and video conferencing aside, most video is not multicast or broadcast, but unicast.
> [...]

Sure, that is a consequence of slow start*, but I argue that having 2ms or 20ms is not going to result in too noticeable a slow down, and bulk transfers like movies really do not care since DASH in all likelihood leaves slow-start for good after the initial ramp-up. Yes, 1ms versus 100ms makes a difference for interactive uses, but putting the CDN in space versus at the base station IMHO is a less clear improvement. Add to this that caches partly work by exploiting "locality", so e.g. for video streaming platforms I expect different countries to have different viewing profiles and hence different content needs to be cached, but satellites cover large "rings" around the world; meaning either you cache everything (or at least the content for your primary market) in space multiple times over so that your main service area is covered at all times or...

I am prepared to eat crow on this in the future, but I am highly skeptical about CDNs in space (in spite of it being a cool project from the technological side).


*) As it looks slow start is getting a bad rep from multiple sides, but I see not better alternative out there that solves the challenge slow-start tackles in a better way. Namely gradual ramping and probing of sending rates/congestion windows to avoid collapse, this in turn means that short flows will never reach capacity, the solution to which might well be, use longer flows then...

  parent reply	other threads:[~2022-09-01  7:58 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2022-08-31 15:22     ` [Starlink] starlink upload behavior Dave Taht
2022-09-01 19:24       ` Luis A. Cornejo
2022-09-01 19:50         ` Dave Taht
2022-08-31  8:15 [Starlink] Starlink "beam spread" David Fernández
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
     [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
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-09-01 15:19 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

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=63B8B233-DF84-4D60-884F-8A83B3ED7607@gmx.de \
    --to=moeller0@gmx.de \
    --cc=david@lang.hm \
    --cc=starlink@lists.bufferbloat.net \
    --cc=u.speidel@auckland.ac.nz \
    /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