Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: libreqos <libreqos@lists.bufferbloat.net>,
	Rpm <rpm@lists.bufferbloat.net>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	Dave Taht <dave.taht@gmail.com>
Cc: Sam Crawford <sam@samknows.com>
Subject: Re: [Starlink] NZ latest latency report
Date: Wed, 5 Jul 2023 21:17:30 +0000	[thread overview]
Message-ID: <SY4PR01MB6979651177BAF4A4CED5B2A2CE2FA@SY4PR01MB6979.ausprd01.prod.outlook.com> (raw)
In-Reply-To: <CAA93jw6A9g4F8z5dUTnv_4oj2wRNWmEmxeRPX=DfDGaCF3jSwg@mail.gmail.com>

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

Sorry have been pretty quiet lately as I've tried to slot some overdue leave in and have been on the road. The most experimenting I've done in the last month has been trying to check out what polar latitude a Ka-band GEO based aircraft WiFi system loses its connectivity at - thanks to Vladimir Putin on a now 14-something hour flight from Haneda to Frankfurt that goes way up there. Answer: somewhere not too far north of Alaska.

NZ broadband survey & Starlink: Pretty much what we saw a few months ago. Given that Starlink seem to manage average load by putting the throttle on subscriptions based on location, I don't expect this to change much longer term either. Goodput depends on how much of a satellite's capacity you can grab, which depends on the number of currently competing users, which they manage closely. Oh and yes the latencies... I suspect that as long as they have full satellite utilisation and the latencies aren't so extreme that they impact on voice / video comms, Starlink will probably just sit pretty, especially if the extra buffering helps absorb windfall load from new handovers.

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

Department of Computer Science

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

The University of Auckland
u.speidel@auckland.ac.nz<mailto:u.speidel@auckland.ac.nz>
http://www.cs.auckland.ac.nz/~ulrich/<http://www.cs.auckland.ac.nz/%7Eulrich/>
****************************************************************
________________________________
From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Sent: Thursday, July 6, 2023 1:08 AM
To: libreqos <libreqos@lists.bufferbloat.net>; Rpm <rpm@lists.bufferbloat.net>; Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Cc: Sam Crawford <sam@samknows.com>
Subject: [Starlink] NZ latest latency report

I do wish that it broke it out by provider, and recommended somehow to
those suffering still, install a better device... VDSL can be made
vastly more tolerable. Otherwise pretty good, and brings in
starlink...

https://comcom.govt.nz/__data/assets/pdf_file/0016/320326/MBNZ-Autumn-Report-28-June-2023.pdf<https://comcom.govt.nz/__data/assets/pdf_file/0016/320326/MBNZ-Autumn-Report-28-June-2023.pdf>

To pick on samknows a little bit, I think the test does not run long
enough, and should be pulling from higher than what appears to be the
75th percentile.



--
Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/<https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937>
Dave Täht CSO, LibreQos
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink<https://lists.bufferbloat.net/listinfo/starlink>

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

  reply	other threads:[~2023-07-05 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 13:08 Dave Taht
2023-07-05 21:17 ` Ulrich Speidel [this message]
2023-07-06  8:20 David Fernández

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=SY4PR01MB6979651177BAF4A4CED5B2A2CE2FA@SY4PR01MB6979.ausprd01.prod.outlook.com \
    --to=u.speidel@auckland.ac.nz \
    --cc=dave.taht@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=rpm@lists.bufferbloat.net \
    --cc=sam@samknows.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