Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Bruce Perens <bruce@perens.com>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: David Lang <david@lang.hm>,
	 "starlink@lists.bufferbloat.net"
	<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink power use & satellite tracking
Date: Sat, 18 Feb 2023 12:13:13 -0800	[thread overview]
Message-ID: <CAK2MWOuUjc-ON7A+DE-RgH2Xeei=N8=4eBia0Fx_aUBrTt0LMA@mail.gmail.com> (raw)
In-Reply-To: <c4f11dc3-7da9-dfc1-54da-936dc56fcb59@auckland.ac.nz>

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

On Sat, Feb 18, 2023 at 4:36 AM Ulrich Speidel via Starlink <
starlink@lists.bufferbloat.net> wrote:

> But now it's within the official specs of 40-75 W most of the
> time, and it's changed this week.


This can be an operating system change implementing low-power sleep when
the system is idle. Often it doesn't happen during initial development.
Hopefully the dish OS is shared with the military and commercial users,
where this can be more important than it is for most residential use.

There's a trick I learned while developing embedded devices. Connect an
oscilloscope across a current shunt feeding the device. You will generally
see the CPU scheduling clock tick at 100 Hz or so, and other periodic power
drains.

    Thanks

    Bruce

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

      reply	other threads:[~2023-02-18 20:13 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
2023-02-18 10:52         ` David Lang
2023-02-18 12:36           ` Ulrich Speidel
2023-02-18 20:13             ` Bruce Perens [this message]

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='CAK2MWOuUjc-ON7A+DE-RgH2Xeei=N8=4eBia0Fx_aUBrTt0LMA@mail.gmail.com' \
    --to=bruce@perens.com \
    --cc=david@lang.hm \
    --cc=starlink@lists.bufferbloat.net \
    --cc=u.speidel@auckland.ac.nz \
    /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