Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Jim Forster <jrforster@mac.com>
To: David Lang <david@lang.hm>
Cc: Dave Taht <dave.taht@gmail.com>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	"Luis A. Cornejo" <luis.a.cornejo@gmail.com>,
	libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [Starlink] [LibreQoS]  Starlink cell capacity (was; tarana strikes back)
Date: Tue, 26 Sep 2023 14:37:18 -0400	[thread overview]
Message-ID: <AD3D5D99-EC21-4C19-B2B1-17DEDF7A502D@mac.com> (raw)
In-Reply-To: <4p971809-5o95-q69q-3r86-48r742ro3215@ynat.uz>

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



> On Sep 25, 2023, at 4:11 AM, David Lang via LibreQoS <libreqos@lists.bufferbloat.net> wrote:
> 
>>>> 
>>>> https://www.taranawireless.com/a-comparison-of-next-generation-fwa-vs-leo-satellite/ <https://www.taranawireless.com/a-comparison-of-next-generation-fwa-vs-leo-satellite/>
>>>> 
>>>> Can anyone question these Starlink numbers for cell size, etc?
> 
> I think they have the cell size reasonably accuarate (for now), But if the cell sizes were of fixed size and unable to be re-used, once there were enough satellites to provide global coverage, adding more would not provide any value. But even their first phase includes many times the number they needed to provide global coverage, so the assumptions around the capacity being fixed by the initial cell size and a single satellite covering it cannot be correct.
> 
> I question the assumption that there will only be a single satellite serving the cell at a time. With directional antennas (including phased arrays) you can aim both your uplink and downlink.
> 
> Even without having multiple satellites covering a single cell, you can shrink the cells by having the ground stations further from the center of the cell aim at different parts of the sky.

This is all true (as much as I understand),  Worth noting as well, is that with LEOs if one satellite is maxed out serving a cell, then getting a second satellite to help with that cell mean adding *lots* more satellites. If adjacent cells had very different loads then I guess nearby unloaeded satellites could help out their busy neighbors.  But areas with busy cells close together would mean doubling the number of satellites and therefore platform Capex.  Whereas terrestrial towers can be densified in busy areas.  


  — Jim




[-- Attachment #2: Type: text/html, Size: 5693 bytes --]

  reply	other threads:[~2023-09-26 18:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24  2:34 [Starlink] tarana strikes back Dave Taht
2023-09-24 20:19 ` Luis A. Cornejo
2023-09-24 20:37   ` Dave Taht
2023-09-25  8:11     ` David Lang
2023-09-26 18:37       ` Jim Forster [this message]
2023-09-26 19:00         ` [Starlink] [LibreQoS] Starlink cell capacity (was; tarana strikes back) David Lang
2023-09-26 21:16           ` Ulrich Speidel
2023-09-26 21:32             ` David Lang
2023-09-27  9:01             ` Alexandre Petrescu
2023-09-26 23:05           ` dan
2023-09-26 19:14 ` [Starlink] tarana strikes back Jeremy Austin

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=AD3D5D99-EC21-4C19-B2B1-17DEDF7A502D@mac.com \
    --to=jrforster@mac.com \
    --cc=dave.taht@gmail.com \
    --cc=david@lang.hm \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=luis.a.cornejo@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