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 12:15:52 +1200	[thread overview]
Message-ID: <ce654e6f-e9b9-4cd5-8bb8-81d06def070e@auckland.ac.nz> (raw)
In-Reply-To: <CAA93jw6A4TNBL5zBFsrJwi3AOjbjun2B98fjyAc3NY0BJsLUPA@mail.gmail.com>

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

On 10/06/2024 11:50 am, Dave Taht via Starlink wrote:
>
> The second set of questions are that the newer, larger Starlink 
> satellites were designed, oh, 4 years ago? with about 4x the capacity 
> of the existing ones, and I imagine (and hope) that they have been 
> continually redesigned with an eye to latency now, as well as capacity.

What do you actually mean by "capacity" here? We have actual numbers in 
terms of what SpaceX are licensed for for user downlink, and that works 
out to be:

 From a V1 or V1.5:

  * no more than 12 Gb/s into a single cell.
  * no more than 16 Gb/s across all user downlink beams.

 From a V2(mini):

  * no more than 20 Gb/s into a single cell on Ku.
  * no more than 48 Gb/s across all beams licensed for Ku user downlink.
  * no more than 25.2 Gb/s across all beams licensed for Ka user
    downlink into a single cell.
  * no more than 99.2 Gb/s across all beams licensed for Ka user downlink.

Note:

  * The current Dishys don't seem to do Ka, at least going by their FCC
    licenses.
  * In Gen 2 systems, there is no longer an explicit distinction made
    between user and gateway downlinks on at least some beams, so the
    above figures assume that all service downlink beams are carrying
    user traffic.
  * The above figure are before any FEC.
  * The single cell limits are independent of the number of satellites
    you deploy - it's the most a cell can get.

But, like you, I'm somewhat intrigued that we haven't see any follow-up 
applications from SpaceX at the FCC for the 3rd generation. 
SAT-LOA-20200526-00055 is four years old, and its latest amendment from 
March this year (unless something's popped up in the last  few weeks) 
relates to their D2D plans only. The latest amendment pertinent to 
Internet things is from August 2021. The gap between Gen 1 
(SAT-LOA-20170726-00110) and Gen 2 (SAT-LOA-20200526-00055) was just 
over three years - and it took almost that long to get 
SAT-LOA-20170726-00110's last modification SAT-MOD-20200417-00037 filed. 
Maybe now that they know that they can get a lift, they will. Or maybe 
they're going flag of convenience and will launch under the Tongan 
regulator, where they've applied for 29,995 satellites, somewhat more 
recently.

-- 

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

School of Computer Science

Room 303S.594 (City Campus)

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



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

  reply	other threads:[~2024-06-10  0:15 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 [this message]
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
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=ce654e6f-e9b9-4cd5-8bb8-81d06def070e@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