Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Oleg Kutkov <contact@olegkutkov.me>
To: BufferBloat List <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink REV4 overview and tests
Date: Sun, 18 Feb 2024 23:47:01 +0200	[thread overview]
Message-ID: <3aca2d2b-44bb-4a4f-96be-df8d3da5307c@olegkutkov.me> (raw)
In-Reply-To: <75e686e8-a4dd-4016-8540-7a4764de6692@olegkutkov.me>

It seems that the latest firmware has some improvements: 
https://i0.wp.com/olegkutkov.me/wp-content/uploads/2024/02/rrul_-_rev4_5776ed0f-38b5-47bf-8ff4-d38f7d2c326b_release.png?ssl=1

300 seconds test: 
https://olegkutkov.me/starlink_rev4_second_test/rrul-2024-02-18T203347.764414.rev4_5776ed0f-38b5-47bf-8ff4-d38f7d2c326b_release.flent.gz

1 minute test: 
https://olegkutkov.me/starlink_rev4_second_test/rrul-2024-02-18T203033.230468.rev4_5776ed0f-38b5-47bf-8ff4-d38f7d2c326b_release.flent.gz

On 2/12/24 23:09, Oleg Kutkov via Starlink wrote:
> All flent files from my tests: 
> https://olegkutkov.me/starlink_rev4_second_test/
>
> rev3/rev4 single test: flent -p all_scaled -l 60 -H 
> netperf-eu.bufferbloat.net
>
> rev3/rev4 2 streams test: flent tcp_2up -p totals -l 60 -H 
> netperf-eu.bufferbloat.net
>                                          flent tcp_2down -p totals -l 
> 60 -H netperf-eu.bufferbloat.net
>
> rev4 with obstructions and with Gen3 router (bypassed and normal): 
> flent rrul -p all_scaled --socket-stats -s 0.5 -l 300 -H 
> netperf-eu.bufferbloat.net
>
> On 2/12/24 03:33, Oleg Kutkov via Starlink wrote:
>> My report on the new terminal: 
>> https://olegkutkov.me/2024/02/12/starlink-terminal-revision-4-overview-and-tests/
>>
>> But more to come.
>>
-- 
Best regards,
Oleg Kutkov


  reply	other threads:[~2024-02-18 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  1:33 Oleg Kutkov
2024-02-12 21:09 ` Oleg Kutkov
2024-02-18 21:47   ` Oleg Kutkov [this message]
2024-02-18 22:25     ` Dave Taht
2024-02-18 23:58       ` Oleg Kutkov

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=3aca2d2b-44bb-4a4f-96be-df8d3da5307c@olegkutkov.me \
    --to=contact@olegkutkov.me \
    --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