From: Sauli Kiviranta <smksauli@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] musk: 28ms median latency on starlink
Date: Sun, 2 Jun 2024 21:17:05 +0300 [thread overview]
Message-ID: <CAJbqEYB2jaFxyFYCohLUrs+g6t9d4niiN3cXY0LDvcGKiQFS7w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5V0JTEgTyn4iuXfrHLNxnKyWDWeZKj_Ao=8OCY_R4fYg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1634 bytes --]
Test 1:
https://www.waveform.com/tools/bufferbloat?test-id=95025c65-684f-4046-a84e-1a09e766b997
Screenshot 2024-06-02 at 20.28.09
Test 2:
https://www.waveform.com/tools/bufferbloat?test-id=0855024d-401c-4b5f-bc83-39d11b831e18
Screenshot 2024-06-02 at 20.30.42
Dishy page started to act wonky so could not run on this machine the native
test. Usually it shows pretty good numbers, maybe a bit optimistic some
times.
On Sun, Jun 2, 2024 at 8:13 PM Dave Taht via Starlink <
starlink@lists.bufferbloat.net> wrote:
> Via elon musk:
>
> Starlink just achieved a new internal median latency record of 28ms
> yesterday! Great work by the engineering and operations teams.
>
> - https://twitter.com/elonmusk/status/1797282250574184587
>
> I of course, am very interested in y'all´s external measurements of how
> well starlink is doing. For me, it is fantastic - 30Mbit uploads nowadays, 0
> latency on the upload (how?)
> https://www.waveform.com/tools/bufferbloat?test-id=2a1d139b-87cb-4ba4-a829-e2167801cffe
>
> I also keep hoping that the rest of the ISP industry is now paying
> attention and deploying stuff like fq_codel and cake and libreqos, but, ah
> well - I will settle for starlink blowing past a lot of dsl and cable and
> finding ways to get their density up.
>
> Anyone going to the Starship launch on the 6th?
>
>
>
> --
> https://www.youtube.com/watch?v=BVFWSyMp3xg&t=1098s Waves Podcast
> Dave Täht CSO, LibreQos
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #1.2: Type: text/html, Size: 3489 bytes --]
[-- Attachment #2: Screenshot 2024-06-02 at 20.28.09.png --]
[-- Type: image/png, Size: 227800 bytes --]
[-- Attachment #3: Screenshot 2024-06-02 at 20.30.42.png --]
[-- Type: image/png, Size: 354024 bytes --]
next prev parent reply other threads:[~2024-06-02 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 17:13 Dave Taht
2024-06-02 18:17 ` Sauli Kiviranta [this message]
2024-06-02 18:23 ` Oleg Kutkov
2024-06-03 10:40 ` Ulrich Speidel
2024-06-03 16:43 ` David Lang
2024-06-03 17:41 ` Mike Puchol
2024-06-03 21:59 ` Ulrich Speidel
2024-06-04 0:08 ` J Pan
2024-06-04 14:53 ` Alexandre Petrescu
2024-06-04 18:24 ` David Lang
2024-06-04 16:33 ` Livingood, Jason
2024-06-04 18:34 ` J Pan
2024-06-05 11:08 ` Alexandre Petrescu
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=CAJbqEYB2jaFxyFYCohLUrs+g6t9d4niiN3cXY0LDvcGKiQFS7w@mail.gmail.com \
--to=smksauli@gmail.com \
--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