Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Mike Puchol <mike@starlink.sx>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] I had forgotten how good this was
Date: Wed, 22 Jan 2025 14:52:57 -0800	[thread overview]
Message-ID: <CAA93jw7o69iwzK0RUqxVuWHbpVN1ybqGmh+BTdHm=0u2qStz1w@mail.gmail.com> (raw)
In-Reply-To: <23793652-9a55-4976-a641-a614cb9f6c96@Spark>

On Mon, Jan 20, 2025 at 11:36 PM Mike Puchol via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> Thank you Dave!
>
> It has been a while since I wrote that piece, and so much has changed. I have been really busy with work, and haven’t been able to implement a lot of these changes into the starlink.sx tracker - I’m trying to put aside some time to update it.

Perhaps someone here could help you out?

>
> The following I can think of:
>
> v2mini satellites are not modeled, and are now a great portion of the constellation.
> Gateways now have Ka and E band capability, increasing backhaul capacity considerably (5 GHz available on E band).

I am under the impression that much of the rocky mountains - eastern
USA can only be served by E and Ka and not Ku?

> Several megasites have been constructed (32 gateway antennas per site).
> Additional Ku beams are available on v2mini satellites.
> ISL is a complete mesh now, with very few gaps.

I keep wondering what tokoyo to london latency is via ISL.

> DTC onboard newer v2mini satellites.
> Reduced operational altitude on some shells, enabling more frequency re-use, and 3-4 dB better link margin.
> New versions of the UT, with Mini being the equivalent of 802.11b Wi-Fi clients ruining the party for G/N clients by dragging down resources.

I thought this would really hurt the constellation initially, but if
you consider most of the time
a dish is idle, not so much.
>
>
>
> Best,
>
> Mike
> On Jan 14, 2025 at 14:24 -0800, Dave Taht via Starlink <starlink@lists.bufferbloat.net>, wrote:
>
> https://mikepuchol.com/modeling-starlink-capacity-843b2387f501
>
> It has a few challengeable assumptions now.
>
> --
> Dave Täht CSO, LibreQos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink



-- 
Dave Täht CSO, LibreQos

  reply	other threads:[~2025-01-22 22:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 22:24 Dave Taht
2025-01-18 21:59 ` Brandon Butterworth
2025-01-21  7:35 ` Mike Puchol
2025-01-22 22:52   ` Dave Taht [this message]
2025-01-23  0:26     ` Ulrich Speidel

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='CAA93jw7o69iwzK0RUqxVuWHbpVN1ybqGmh+BTdHm=0u2qStz1w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=mike@starlink.sx \
    --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