From: Nathan Owens <nathan@nathan.io>
To: Darrell Budic <budic@onholyground.com>
Cc: Dave Taht <dave.taht@gmail.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink throughput / bufferbloat change?
Date: Sun, 27 Jun 2021 20:20:23 -0600 [thread overview]
Message-ID: <CALjsLJvrYqu9yKmLDqbNf0U66iHHnA23+CsX6QTO68gRSTZoQA@mail.gmail.com> (raw)
In-Reply-To: <CE32F49F-909E-44F7-8BAC-051DB4967750@onholyground.com>
[-- Attachment #1: Type: text/plain, Size: 2419 bytes --]
My dish has not been upgraded yet, I'm still on
a4908729-5051-4d3b-aacc-446ef9b26cdc.uterm.release
My "obstructed" seconds keep creeping up, was 0 for a while, then 0-4s for
a while, now up to ~55s
On Sun, Jun 27, 2021 at 7:26 PM Darrell Budic <budic@onholyground.com>
wrote:
> Hey Dave, how’d those tests look yesterday (sqm enabled though) vs today
> (disabled)? Looks like my dishy upgraded to
>
> 4990ce8d-5028-4e51-a015-e9ab1b1ebe1a.uterm.release
>
> around 4:30AM CDT this morning.
>
> Nathan, did you get a chance to check versions or uptime? Probably worth
> tracking if we’re looking for performance changes.
>
> On Jun 26, 2021, at 9:24 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
>
> I have fired off a new string of tests. should be done in an hour.
>
> I don't know if budic has sqm on or off at the moment.
>
> On Sat, Jun 26, 2021 at 7:10 AM Jared Mauch <jared@puck.nether.net> wrote:
>
>
> I will be able to test perhaps in 6-10 hours as I'll be getting the system
> online hopefully.
>
> Sent from my TI-99/4a
>
> On Jun 26, 2021, at 9:38 AM, Nathan Owens <nathan@nathan.io> wrote:
>
>
> 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
> _______________________________________________
> 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
>
>
>
>
> --
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>
> Dave Täht CTO, TekLibre, LLC
> _______________________________________________
> 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: 5002 bytes --]
prev parent reply other threads:[~2021-06-28 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 13:38 Nathan Owens
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 [this message]
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=CALjsLJvrYqu9yKmLDqbNf0U66iHHnA23+CsX6QTO68gRSTZoQA@mail.gmail.com \
--to=nathan@nathan.io \
--cc=budic@onholyground.com \
--cc=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