Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Comprehensive Measurement Study on Starlink Performance Published
Date: Mon, 26 Feb 2024 15:19:07 -0800 (PST)	[thread overview]
Message-ID: <28ro46p9-5620-9qr2-829q-3s0on13q6po6@ynat.uz> (raw)
In-Reply-To: <e30425e2-8241-4799-85e6-2b11e80641f0@auckland.ac.nz>

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

On Tue, 27 Feb 2024, Ulrich Speidel via Starlink wrote:

> My most serious concern about Starlink as a system remains the fact that it 
> puts a pipe between the end user and the first network hop (the satellite) 
> that is in principle very difficult to scale: There's only so much extra 
> spectrum one can use, spatial diversity (beamforming) has limited potential, 
> and unlike in cellular networks, you can't really shrink the cell size to 
> accommodate more end users through frequency re-use as your cell size is 
> determined to a good part by orbital altitude. That all but rules out the 
> scaling effects that CDNs have brought to the rest of the Internet, which 
> keep orders of magnitude worth of traffic off long distance cables. There 
> simply isn't an obvious place in LEO topology to put a cache that'll produce 
> a decent number of hits while being able to serve this content to end users 
> through a large collective bandwidth.
>
> The interesting question for me is how much we can scale Starlink and its 
> up-and-coming cousins from the few million users Starlink has now. To 100 
> million? To 200 million? Half a billion even?

If you are in an area where the cell companies are investing in smaller cells, 
then you are not in a Starlink target area. There are large areas with poor or 
non-existant cell coverage.

Outside the US, scaling of Starlink can happen just by providing coverage to 
locations that don't yet have coverage with no additional satellites.

In terms of scaling existing areas, larger antennas can reduce cell size, you 
can have more than one satellite cover a given cell, they are looking at 
eventually having lower satellites, which again will let them reduce the cell 
size.

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:[~2024-02-26 23:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 18:12 Nitinder Mohan
2024-02-26 19:49 ` J Pan
2024-02-26 19:53 ` Dave Taht
2024-02-26 22:19 ` Ulrich Speidel
2024-02-26 23:19   ` David Lang [this message]
2024-02-27  0:16     ` Ulrich Speidel
2024-02-27  1:13       ` David Lang
2024-02-27  2:33         ` Ulrich Speidel
2024-02-27  6:21           ` David Lang
2024-02-27  7:31             ` [Starlink] starlink business peering Dave Taht
2024-02-27  7:38               ` David Lang
2024-02-27  7:42               ` Dave Taht
2024-02-27  8:08                 ` David Lang
2024-02-27 11:15             ` [Starlink] Comprehensive Measurement Study on Starlink Performance Published Ulrich Speidel
2024-02-27 14:02               ` Nitinder Mohan

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=28ro46p9-5620-9qr2-829q-3s0on13q6po6@ynat.uz \
    --to=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