From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] capturing some cake-mq requirements
Date: Sun, 3 Sep 2023 08:48:59 -0700 [thread overview]
Message-ID: <CAA93jw6GQaagQimXAonhQdKHeo+p7wkcTY2=bsAN2OPFL4oA4Q@mail.gmail.com> (raw)
I have been writing down some requirements for a new version of the
CAKE qdisc based on observed results from the field.
I apologize for the somewhat random nature of this (and there are a
great deal of outstanding comments on it - we seem to be seeing some
issues with steam and ecn),
I tend to write first and polish later. I started putting in some
observations about starlink´s behaviors and how to possibly fix them,
towards the end, in thinking about adding a "plug" facility to it in
particular.
https://docs.google.com/document/d/1tTYBPeaRdCO9AGTGQCpoiuLORQzN_bG3TAkEolJPh28/edit
Anyway, if you don´t feel like wading through that mess:
In looking over my starlink data accumulated in the last couple weeks
I am seeing that 70ms spike more regularly, and I am curious if it is
appearing in other data?
Why are the steps in baseline latency are so large? Could they be
doing something further to delay the packets and deal with the doppler
that way?
I keep hoping that a good video conferencing analysis tool would show
up that would show glitches per minute and the recovery period for
each glitch.
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
reply other threads:[~2023-09-03 15:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw6GQaagQimXAonhQdKHeo+p7wkcTY2=bsAN2OPFL4oA4Q@mail.gmail.com' \
--to=dave.taht@gmail.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