Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: warren ponder <wponder11@gmail.com>
Cc: Starlink-Bufferbloat <starlink@lists.bufferbloat.net>,
	Andrew Somerville <aesomerville@gmail.com>
Subject: Re: [Starlink] CAKE-Autorate
Date: Thu, 1 Dec 2022 21:40:02 +0100	[thread overview]
Message-ID: <DEFD81B0-E0BC-41E7-BCB9-1446789C963D@gmx.de> (raw)
In-Reply-To: <CACnq21eNQ32Q4m3AGjJvVK9yAviPaD3cdc+qMZFAUf0nGGbkRw@mail.gmail.com>

Hi Warren,


> On Dec 1, 2022, at 19:41, warren ponder via Starlink <starlink@lists.bufferbloat.net> wrote:
> 
> I have been working with the 3rd party router team of the router I
> have been using behind Starlink to add CAKE to their router. I have an
> early access loaded and have modified it to add CAKE-Autorate. I have
> it running but not entirely sure I have it all running correctly or
> how to quantify if its making a difference.
> 
> Beside github for CAKE-Autorate are there any other sources of info to
> read up on about ensuring I have it going right and possibly quantify
> its making a difference?

	Most discussion happens in the following OpenWrt thread:
https://forum.openwrt.org/t/cake-w-adaptive-bandwidth/135379/1202
or you can open an issue in the github. About making a difference we added some potting code which can turn the log files into partially interpretable plots.

I use (192.168.42.1 is my OpenWrt/TurrisOS router running cake-autorate):
ssh root@192.168.42.1 'kill -USR1 $( cat /var/run/cake-autorate/maintain_log_file_pid )'  && sleep 30 && scp  root@192.168.42.1:/var/log/cake-autorate_*.log.gz ./SCRATCH/ && ssh root@192.168.42.1 'rm /var/log/cake-autorate_*.log.gz'

followed by:
octave -qf --eval 'fn_parse_autorate_log("./SCRATCH/cake-autorate_2022-12-01_20_21_16.log.gz", [], [])'

this requires octave >= 6.4... once you have that post your plots to the forum thread and we can take it from there.



Regards
	Sebastian

P.S.: I cc'd Andrew cake-autorate's principal developer, he might have more ideas...



> 
> thanks
> 
> WP
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink


  reply	other threads:[~2022-12-01 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 18:41 warren ponder
2022-12-01 20:40 ` Sebastian Moeller [this message]
2022-12-01 20:52   ` warren ponder
2022-12-01 21:25     ` Sebastian Moeller
2022-12-02 13:08     ` Andrew Somerville
2022-12-02 13:19       ` warren ponder

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=DEFD81B0-E0BC-41E7-BCB9-1446789C963D@gmx.de \
    --to=moeller0@gmx.de \
    --cc=aesomerville@gmail.com \
    --cc=starlink@lists.bufferbloat.net \
    --cc=wponder11@gmail.com \
    /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