Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starship's 4th flight test was magnificent
Date: Mon, 10 Jun 2024 23:04:00 +1200	[thread overview]
Message-ID: <8986fa02-3c6a-4d66-9105-979d7e4ef248@auckland.ac.nz> (raw)
In-Reply-To: <qn3ro633-q7n7-1oq4-5295-s01on981ss5s@ynat.uz>

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

On 10/06/2024 2:38 pm, David Lang via Starlink wrote:
>
> the V2 were about 8-10x the capacity of the V1.5 (the ones they could 
> launch 50-60 per flight), the v2 mini they have been launching 
> (~22/flight) are about midway between the two. No recent word on the 
> V2s, but Tim Dodd did another starbase visit with Elon before the 
> flight, so watch for that to show up soon.

I think it'd be useful we could agree on what we mean by "capacity" 
before we start throwing numbers around, especially relative ones. For 
Starlink, I can think of the following capacities (yes, plural):

  * User up-/downlink capacity from/to a single user. (How many bits/s
    can I throw at a Dishy?)
  * Downlink capacity to all users in a single cell (under the proviso
    that we don't have any users in adjacent cells that need / want
    service - think small island in the middle of the Pacific).
  * Overall user downlink capacity from a single satellite to multiple
    cells. (Can't deploy co-frequency beams with identical polarisation
    to the same cell if you have multiple such beams on your bird, but
    can do so if we can aim them at different cells)
  * Gateway uplink capacity (to users served directly by the satellite
    or indirectly via ISLs)
  * Gateway downlink (from users served directly by the satellite or
    indirectly via ISLs)
  * Dto. per gateway (see co-frequency beam issue)
  * Processing capacity: Number of bits / s that a satellite can pump
    between its receive beams / incoming ISLs and transmit beams /
    outgoing ISLs.

It's getting late and I probably forgot one or two ;-)


-- 

****************************************************************
Dr. Ulrich Speidel

School of Computer Science

Room 303S.594 (City Campus)
Ph: (+64-9)-373-7599 ext. 85282

The University of Auckland
ulrich@cs.auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************

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

  reply	other threads:[~2024-06-10 11:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 23:50 Dave Taht
2024-06-10  0:15 ` Ulrich Speidel
2024-06-10  2:22 ` Michael Richardson
2024-06-10 10:51   ` Ulrich Speidel
2024-06-10 12:04     ` David Lang
2024-06-10 12:15       ` Ulrich Speidel
2024-06-10  2:38 ` David Lang
2024-06-10 11:04   ` Ulrich Speidel [this message]
2024-06-10 12:06     ` David Lang
2024-06-10 12:21       ` Ulrich Speidel
2024-06-10  8:57 ` Alexandre Petrescu
2024-06-10  9:49   ` David Lang
2024-06-10 13:22     ` Alexandre Petrescu
2024-06-10 13:37       ` David Lang

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=8986fa02-3c6a-4d66-9105-979d7e4ef248@auckland.ac.nz \
    --to=u.speidel@auckland.ac.nz \
    --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