From: Dave Taht <dave.taht@gmail.com>
To: "Jonas Mårtensson" <martensson.jonas@gmail.com>
Cc: "Jonathan Morton" <chromatix99@gmail.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
conor@conorbeh.com, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] starlink
Date: Sat, 12 Dec 2020 12:40:22 -0800 [thread overview]
Message-ID: <CAA93jw461bZn0P2eXGEOTE2DhOm6ie07-iN0S_JYehibupm1TA@mail.gmail.com> (raw)
In-Reply-To: <CAM9iV=+Rxh4svpHhHCPN=fWg7c4+XkzJBop=W4Hk7ge1F99_vg@mail.gmail.com>
Sigh. On the plus side the hardware in use on the UFO is a pretty good
QCA platform. It is speculated
on another thread that it actually runs openwrt. So with a few
soldiered on pins to get at a serial port
or figuring out some other way into the box.... we could make a dent in this.
On Thu, Dec 3, 2020 at 12:38 AM Jonas Mårtensson
<martensson.jonas@gmail.com> wrote:
>
> > Thanks for sharing! That is some terrible bloat, though! :(
>
> Also widely varying download speed.
>
> > 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.
>
> I'm not the OP but from the reddit thread (https://www.reddit.com/r/Starlink/comments/k0dwon/starlink_and_bufferbloat_testing/.compact), this is their dslreports test:
>
> http://www.dslreports.com/speedtest/66406433
>
> It does look like the main problem is in the uplink. The download speed looks much more consistent in the dslreports test but I guess that could also be due to the short duration of the test.
>
> Another user from the reddit thread showing similar results:
>
> http://www.dslreports.com/speedtest/66406098
>
> /Jonas
>
> On Tue, Dec 1, 2020 at 3:39 PM Jonathan Morton <chromatix99@gmail.com> wrote:
>>
>> > 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
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-12-12 20:40 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
2020-12-03 8:38 ` Jonas Mårtensson
2020-12-12 20:40 ` Dave Taht [this message]
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=CAA93jw461bZn0P2eXGEOTE2DhOm6ie07-iN0S_JYehibupm1TA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=conor@conorbeh.com \
--cc=martensson.jonas@gmail.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