Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jared Mauch <jared@puck.nether.net>
Cc: Nathan Owens <nathan@nathan.io>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink throughput / bufferbloat change?
Date: Sat, 26 Jun 2021 07:24:38 -0700	[thread overview]
Message-ID: <CAA93jw7cNCCgEMJs6nSWGUAPbYV+dxDK9z4Ow46xwJZ+vN2fgg@mail.gmail.com> (raw)
In-Reply-To: <7664DBDE-5049-498A-9C40-4CF17FA2D488@puck.nether.net>

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

  reply	other threads:[~2021-06-26 14:24 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 [this message]
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=CAA93jw7cNCCgEMJs6nSWGUAPbYV+dxDK9z4Ow46xwJZ+vN2fgg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=jared@puck.nether.net \
    --cc=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