From: Nathan Owens <nathan@nathan.io>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Starlink throughput / bufferbloat change?
Date: Sat, 26 Jun 2021 06:38:08 -0700 [thread overview]
Message-ID: <CALjsLJvfnSD8X7UuPzZKdvKOtOS0kqdVm7uwDMUFGWsQMrcVaQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
I'm on vacation, so I can't do a ton of testing, but it seems like in the
last ~2 days, my DL speeds are lower (<160Mbps, generally 90-110Mbps), but
download-induced bufferbloat is also greatly reduced (Latency generally
<60ms, with small spikes up to maybe 150ms more rarely -- much better than
to up to 400ms I was seeing before).
I confirmed the same behavior with one other list member, has anyone else
seen similar?
--Nathan
[-- Attachment #2: Type: text/html, Size: 536 bytes --]
next reply other threads:[~2021-06-26 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 13:38 Nathan Owens [this message]
2021-06-26 14:09 ` Jared Mauch
2021-06-26 14:24 ` Dave Taht
2021-06-28 1:26 ` Darrell Budic
2021-06-28 1:38 ` Dave Taht
2021-06-28 2:20 ` Nathan Owens
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=CALjsLJvfnSD8X7UuPzZKdvKOtOS0kqdVm7uwDMUFGWsQMrcVaQ@mail.gmail.com \
--to=nathan@nathan.io \
--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