General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Conor Beh <conor@conorbeh.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] starlink
Date: Tue, 1 Dec 2020 16:39:11 +0200	[thread overview]
Message-ID: <FBB2D1DA-C3BE-4975-9F0A-FD9D25C7885C@gmail.com> (raw)
In-Reply-To: <87tut51x3j.fsf@toke.dk>

> On 1 Dec, 2020, at 3:20 pm, Toke Høiland-Jørgensen via Bloat <bloat@lists.bufferbloat.net> wrote:
> 
>> Jim Gettys made a reddit post on r/Starlink asking for data from beta
>> testers. I am one of those testers. I spun up an Ubuntu VM and did three
>> runs of flent and rrul as depicted in the getting started page. You may
>> find the results here:
>> https://drive.google.com/file/d/1NIGPpCMrJgi8Pb27t9a9VbVOGzsKLE0K/view?usp=sharing
> 
> Thanks for sharing! That is some terrible bloat, though! :(

I imagine it exists in the uplink device rather than the Starlink network itself.  Distinct upload and download bloat tests would help in determining whether it's at your end or the remote end.  You should be able to use dslreports.com/speedtest to determine that.

 - Jonathan Morton

  reply	other threads:[~2020-12-01 14:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 23:19 Conor Beh
2020-12-01 13:20 ` Toke Høiland-Jørgensen
2020-12-01 14:39   ` Jonathan Morton [this message]
2020-12-03  8:38     ` Jonas Mårtensson
2020-12-12 20:40       ` Dave Taht
2020-12-01 14:02 ` Michael Richardson

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FBB2D1DA-C3BE-4975-9F0A-FD9D25C7885C@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=conor@conorbeh.com \
    --cc=toke@toke.dk \
    /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