From: Nathan Owens <nathan@nathan.io>
To: Dave Taht <davet@teklibre.net>
Cc: Darrell Budic <budic@onholyground.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dynamically adjusting cake to starlink
Date: Wed, 9 Jun 2021 05:09:11 -0700 [thread overview]
Message-ID: <CALjsLJv_uvsTq3e9rcxSCjzNKPmdqfiOojDx517ug5ti65BmtQ@mail.gmail.com> (raw)
In-Reply-To: <AB233C27-07F0-4D2C-A433-4E6C0D64299A@teklibre.net>
[-- Attachment #1: Type: text/plain, Size: 2944 bytes --]
This one’s probably not a Mike question since the site doesn’t pull
anything from dishy. The dish represents all of its stats via gRPC - there
are several clients available. I can probably code this up next week if
someone doesn’t beat me to it.
—Nathan
On Wed, Jun 9, 2021 at 2:12 AM Dave Taht <davet@teklibre.net> wrote:
> Dear Mike:
>
> The biggest thing we need is something that can pull the right stats off
> the dishy and dynamically adjust cake (on outbound at least) to have the
> right amount of buffering for the available bandwidth, so as to make for
> better statistical multiplexing (FQ) and active queue management (AQM)
>
> It’s pretty simple: in mangled shell script syntax:
>
> while up, down = getstats()
> do
> tc qdisc change dev eth0 root cake bandwidth $up
> tc qdisc change dev ifb0 root cake bandwidth $down
> done
>
> Which any router directly in front of the dishy can do (which is what
> we’ve been doing)
>
> But whatever magic “getstats()” would need to do is unclear from the stats
> we get out of it, and a better alternative would be for the dishy itself
> and their headends to be doing this with “BQL" backpressure.
>
> As for the huge reductions of latency and jitter under working load, and a
> vast improvement in QoE - for what we’ve been able to achieve thus far, see
> appendix A here:
>
>
> https://docs.google.com/document/d/1rVGC-iNq2NZ0jk4f3IAiVUHz2S9O6P-F3vVZU2yBYtw/edit?usp=sharing
>
> We’ve got plenty more data
> on uploads and downloads and other forms of traffic (starlink is
> optimizing for ping, only, over ipv6. Sigh)…
>
> … and a meeting with some starlink execs at 11AM today.
>
> I’m pretty sure at this point we will be able to make a massive
> improvement in starlink’s network design very quickly, after that meeting.
>
> On Jun 8, 2021, at 2:54 PM, Nathan Owens <nathan@nathan.io> wrote:
>
> I invited Mike, the creator of the site (starlink.sx) to join the list -
> he’s put a crazy amount of work in to figure out which sats are active
> (with advice from Jonathan McDowell), programming GSO exclusion bands, etc.
> His dayjob is in the ISP business.
>
> On Sat, Jun 5, 2021 at 8:31 PM Darrell Budic <budic@onholyground.com>
> wrote:
>
>> https://starlink.sx if you have’t seen it yet. You can locate yourself,
>> and it will make some educated guesses about which satellite to which
>> ground station you’re using. Interesting to see the birds change and the
>> links move between ground stations, lots going on to make these things work.
>> _______________________________________________
>> 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
>
>
>
[-- Attachment #2: Type: text/html, Size: 4600 bytes --]
next prev parent reply other threads:[~2021-06-09 12:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 3:31 [Starlink] pretty cool starlink visualizer Darrell Budic
2021-06-06 4:26 ` David Lang
2021-06-08 21:54 ` Nathan Owens
2021-06-09 9:12 ` [Starlink] dynamically adjusting cake to starlink Dave Taht
2021-06-09 10:20 ` Mikael Abrahamsson
2021-06-09 16:39 ` Michael Richardson
2021-06-09 18:10 ` David Lang
2021-06-09 12:09 ` Nathan Owens [this message]
2021-06-09 12:16 ` Mike Puchol
2021-06-09 13:21 ` Dave Taht
2021-06-09 14:12 ` Michael Richardson
2021-06-09 15:23 ` Mike Puchol
2021-06-09 21:18 ` Michael Richardson
2021-06-09 21:36 ` Nathan Owens
2021-06-09 23:37 ` Mike Puchol
2021-06-09 15:32 ` Nathan Owens
2021-06-09 15:46 ` 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=CALjsLJv_uvsTq3e9rcxSCjzNKPmdqfiOojDx517ug5ti65BmtQ@mail.gmail.com \
--to=nathan@nathan.io \
--cc=budic@onholyground.com \
--cc=davet@teklibre.net \
--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