Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Bruce Perens <bruce@perens.com>,
	"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink power use & satellite tracking
Date: Sat, 18 Feb 2023 23:25:12 +1300	[thread overview]
Message-ID: <59d5e2b7-ee1e-9019-fb98-3a81fd8bf545@auckland.ac.nz> (raw)
In-Reply-To: <20200.1676648584@localhost>

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

I'd expect higher saturation to be associated with the use of fewer 
satellites per user terminal, and therefore lower power use.

Similarly, I'd expect proximity to gateways to be associated with higher 
power use.

What leads me to this impression?

Essentially, inter-satellite linking isn't yet in widespread use for 
Starlink, so most users at this point still use a bent-pipe arrangement 
terminal<->satellite<->gateway<->Internet.

This requires the satellite to be in view of both terminal and gateway. 
There is, however, no reason why a user's packets could not travel via a 
diversity of satellites. The only requirement for this arrangement is 
that the satellites used must be in the intersection of the set of 
satellites that the terminal can see and the set of satellites that the 
gateway can see.

What makes me think that this is actually happening? I'm in a low 
saturation cell close to multiple gateways and partial obstruction of 
the southern sky (which dishy uses in the southern hemisphere). So 
whatever satellite my dishy sees, the gateways also see (more or less), 
but the number of satellites I see is constrained by the partial 
obstruction, so jumps up and down over short periods of time as the 
satellites move in and out of view for me.

When I look at achievable rates with the likes of speedtest.net then I 
see huge jumps over relatively short periods of time. 20-30 Mb/s down 
one moment, 160+ Mb/s in the next run. This is exactly what I'd expect 
if dishy moves from a set of satellites with plenty of competition from 
neighbouring rural regions (e.g., satellites south-east of Auckland) to 
a larger set predominantly over the Tasman Sea, where there are no 
users. I'm simplifying here.

So if you happen to be a nerd in a fibre-connected and -penetrated city 
surrounded by gateways, you should see higher power use as Starlink 
wants you to have the maximum rate possible and will let you access 
whichever birds are available during the current time period. If you're 
in the wap-waps with your nearest gateway 100's of kilometres away (or 
miles for youse Americans and Brits, we're talking ballpark here ;-)), 
then the number of satellites you see that can relay to gateways for you 
should be smaller on average. You would be facing stiff competition for 
their capacity from your neighbours down the road. That would give you 
less chance to transmit, and hence lower power use. Note: A mitigating 
factor here could also be that the beams you need to communicate with 
these relaying satellites from your dishy might be further off bore than 
in the former case, which would require a little extra power to make up 
for longer path and lower dishy aperture.

Hope that makes sense?

On 18/02/2023 4:43 am, Michael Richardson wrote:
>
> Ulrich Speidel via Starlink <starlink@lists.bufferbloat.net> wrote:
> > * Whether you consider your cell Starlink virgin territory or close to
> > subscriber saturation (https://www.starlink.com/map 
> <https://www.starlink.com/map> 
> might help
> > determine that - if it's light blue, it's likely the former, if it's
> > "waitlist" blue but surrounded by light blue areas, or rural and
>
> What's the expected corrolation?
> Higher saturation => higher current? Or the opposite?
>
-- 
****************************************************************
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: 4751 bytes --]

  parent reply	other threads:[~2023-02-18 10:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 23:08 Ulrich Speidel
2023-02-16 23:12 ` Nathan Owens
2023-02-16 23:14   ` Nathan Owens
2023-02-16 23:25     ` Jonathan Bennett
2023-02-16 23:23 ` David Lang
2023-02-16 23:36   ` David Lang
2023-02-17  1:24 ` Bruce Perens
2023-02-17  5:27   ` Ulrich Speidel
2023-02-17  5:31     ` Nathan Owens
2023-02-17 15:43     ` Michael Richardson
2023-02-17 19:13       ` Bruce Perens
2023-02-18 10:25       ` Ulrich Speidel [this message]
2023-02-18 10:52         ` David Lang
2023-02-18 12:36           ` Ulrich Speidel
2023-02-18 20:13             ` Bruce Perens

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=59d5e2b7-ee1e-9019-fb98-3a81fd8bf545@auckland.ac.nz \
    --to=u.speidel@auckland.ac.nz \
    --cc=bruce@perens.com \
    --cc=mcr@sandelman.ca \
    --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