From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] some more starlink fun latency vs load plots
Date: Thu, 7 Jul 2022 11:27:59 -0700 [thread overview]
Message-ID: <CAA93jw5ABL8qhwm95O3bmq_4oLDowmZzSenbzBGsh17g9UMZkw@mail.gmail.com> (raw)
https://forum.openwrt.org/t/cake-w-adaptive-bandwidth/108848/3257
My favorites though are further up that link where we plot a highres
isochronous signal against other traffic. I'm just dying
to see lte (esp with movement), plotted this way also.
In starlink's defense this is still so massively better than lte and
most wifi, but I am compelled to perpetually point out
it could be the best in the world, as elsewhere we are finally making
some good progress on resolving 5 interrelated regressions in
openwrt's fq-codel'd and ATF wifi codebase.
https://forum.openwrt.org/t/aql-and-the-ath10k-is-lovely/59002/621
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2022-07-07 18:28 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=CAA93jw5ABL8qhwm95O3bmq_4oLDowmZzSenbzBGsh17g9UMZkw@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