Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Bjørn Ivar Teigen" <bjorn@domos.no>
Cc: starlink@lists.bufferbloat.net, Geoff Huston <gih@apnic.net>
Subject: Re: [Starlink] Good APNIC blog on Starlink, testing Cubic, Reno, and BBR
Date: Fri, 6 May 2022 11:05:33 -0700	[thread overview]
Message-ID: <CAA93jw55MqnMpm5mFXn806r9Mt0ZVPE116HCNFmVRdibC5OR+g@mail.gmail.com> (raw)
In-Reply-To: <CAKf5G6JrK9zDH8MDMQyC-23TUAHQOYFF2yfLWbt9PjDDxe72Wg@mail.gmail.com>

Nice work Geoff!

What is it that people so love and trust about iperf3? (this is a
serious question, as I did not trust a multiplicity of iperfs methods
10 years ago, and while I know it has evolved, have not tested with it
recently vs a vs flent & netperf)

I was primarily looking at starlink upload speeds and delays with this document:

https://docs.google.com/document/d/1puRjUVxJ6cCv-rgQ_zn-jWZU9ae0jZbFATLf4PQKblM/edit

But I haven't refreshed it. The nice thing about testing uplink
performance is you can more easily sample and control various tcp
parameters like pacing_rate, etc, as well as vary the underlying
qdisc.

There's a flent server available at sydney.starlink.taht.net if you'd
like to try it.

On Thu, May 5, 2022 at 12:06 AM Bjørn Ivar Teigen <bjorn@domos.no> wrote:
>
> I think some of you might enjoy this: https://blog.apnic.net/2022/05/02/testing-leo-and-geo-satellite-services-in-australia/

Really good, solid work. I think he may have run into TSQ to some extent.


>
> No working latency tests, but a great intro to the tech and interesting TCP test results.
>
> Cheers,
> Bjørn Ivar Teigen
> --
> Bjørn Ivar Teigen
> Head of Research
> +47 47335952 | bjorn@domos.no | www.domos.no
> WiFi Slicing by Domos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink



-- 
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC

  reply	other threads:[~2022-05-06 18:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05  7:06 Bjørn Ivar Teigen
2022-05-06 18:05 ` Dave Taht [this message]
2022-05-06 18:28   ` Dave Taht
2022-05-13  1:39 ` [Starlink] ch-ch-ch-ch-changes! Bruce Perens
2022-05-13  2:27   ` David Lang
2022-05-13 16:07   ` Mr. Clif
2022-05-13 16:09     ` Nathan Owens
2022-05-13 17:28       ` Bruce Perens
2022-05-23  1:51         ` Mr. Clif

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=CAA93jw55MqnMpm5mFXn806r9Mt0ZVPE116HCNFmVRdibC5OR+g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bjorn@domos.no \
    --cc=gih@apnic.net \
    --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