Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] It's still the starlink latency...
Date: Mon, 17 Oct 2022 18:53:50 +0200	[thread overview]
Message-ID: <CAC=tZ0pnXrhf7iuJ72ZrXCdVwGjQqTnfUaVGzjtMBGxFrQ8y8w@mail.gmail.com> (raw)
In-Reply-To: <CAC=tZ0pzfG9kVBtNe870DxJCPkWdP2pfLj1RonhbSyx9wWS5vQ@mail.gmail.com>

Another report, linked from the MIT one previously mentioned is also
very interesting. In page 29 it compiles a series of latency
measurement tools, including flent, that has been mentioned in this
list before:
https://www.bitag.org/latency-explained.php

2022-10-17 15:50 GMT+02:00, David Fernández <davidfdzp@gmail.com>:
> That MIT paper is really interesting, yes, thank you.
>
> Have you ever heard about the Network Performance Score (NPS), based
> on ETSI TR 103 559?
>
> That could be the kind of nutriscore equivalent for networks that they
> are searching for  on that paper.
>
> The NPS is proposed for 5G networks, but well, Starlink could be
> scored too, as 5G networks are mobile wireless Internet access
> networks, like Starlink.
>
> https://www.rohde-schwarz.com/nl/solutions/test-and-measurement/mobile-network-testing/network-performance-score/network-performance-score_250678.html
>
> Unfortunately, I am not aware of any tool, besides that one from R&S,
> to measure the NPS or the interactivity score of a network:
> https://www.rohde-schwarz.com/uk/solutions/test-and-measurement/mobile-network-testing/stories-insights/article-interactivity-test-concept-and-kpis-part-2-_253245.html
>
> I am aware only of similar tools to measure interactivity, such as
> these for TWAMP (RFC 5357):
> https://github.com/nokia/twampy
> https://github.com/tcaine/twamp
> https://github.com/emirica/twamp-protocol
>
> Then, the UDP ping: http://perform.wpi.edu/downloads/#udp
>
> Regards,
>
> David
>
>> Date: Thu, 22 Sep 2022 08:26:08 -0700
>> From: Dave Taht <dave.taht@gmail.com>
>> To: warren ponder <wponder11@gmail.com>
>> Cc: Mike Puchol <mike@starlink.sx>,  Dave Täht via Starlink
>> 	<starlink@lists.bufferbloat.net>
>> Subject: Re: [Starlink] It's still the starlink latency...
>> Message-ID:
>> 	<CAA93jw4V_3qmdcwMnTrRw0x18DSwds1OG1sh0aY3+aL+niSVEA@mail.gmail.com>
>> Content-Type: text/plain; charset="UTF-8"
>>
>> This MIT paper went by today. It's really good.
>>
>> https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4178804
>>
>>
>

  reply	other threads:[~2022-10-17 16:53 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 13:50 David Fernández
2022-10-17 16:53 ` David Fernández [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-29  9:10 David Fernández
2022-09-29 19:34 ` Eugene Chang
2022-09-21 18:35 Dave Taht
2022-09-22 11:41 ` Andrew Crane
2022-09-22 12:01   ` Mike Puchol
2022-09-22 13:46     ` warren ponder
2022-09-22 15:07       ` Dave Taht
2022-09-22 15:26         ` Dave Taht
2022-09-26 15:20 ` Livingood, Jason
2022-09-26 15:29   ` Dave Taht
2022-09-26 15:57     ` Sebastian Moeller
2022-09-26 16:21     ` Dave Taht
2022-09-26 16:32       ` Bruce Perens
2022-09-26 19:59         ` Eugene Chang
2022-09-26 20:04           ` Bruce Perens
2022-09-26 20:14             ` Ben Greear
2022-09-26 20:24               ` Bruce Perens
2022-09-26 20:32                 ` Dave Taht
2022-09-26 20:36                   ` Bruce Perens
2022-09-26 20:47                 ` Ben Greear
2022-09-26 20:19             ` Eugene Y Chang
2022-09-26 20:28               ` Dave Taht
2022-09-26 20:32                 ` Bruce Perens
2022-09-26 20:35               ` Bruce Perens
2022-09-26 20:48               ` David Lang
2022-09-26 20:54                 ` Eugene Y Chang
2022-09-26 21:01                   ` Sebastian Moeller
2022-09-26 21:10                     ` Eugene Y Chang
2022-09-26 21:20                       ` Sebastian Moeller
2022-09-26 21:35                         ` Eugene Y Chang
2022-09-26 21:44                           ` David Lang
2022-09-26 21:44                           ` Bruce Perens
2022-09-27  0:35                             ` Dave Taht
2022-09-27  0:55                               ` Bruce Perens
2022-09-27  1:12                                 ` Dave Taht
2022-09-27  4:06                               ` Eugene Y Chang
2022-09-27  3:50                             ` Eugene Y Chang
2022-09-27  7:09                               ` Sebastian Moeller
2022-09-27 22:46                                 ` Eugene Y Chang
2022-09-28  9:54                                   ` Sebastian Moeller
2022-09-28 18:49                                     ` Eugene Y Chang
2022-09-26 21:22                       ` David Lang
2022-09-26 21:29                         ` Sebastian Moeller
2022-09-27  3:47                           ` Eugene Y Chang
2022-09-27  6:36                             ` Sebastian Moeller
2022-09-27 13:55                               ` Dave Taht
2022-09-28  0:20                                 ` Eugene Y Chang
2022-09-26 21:02                   ` Bruce Perens
2022-09-26 21:14                     ` Dave Taht
2022-09-26 21:10                   ` Dave Taht
2022-09-26 21:28                     ` warren ponder
2022-09-26 21:34                       ` Bruce Perens
2022-09-27 16:14                       ` Dave Taht
2022-09-26 21:17                   ` David Lang

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='CAC=tZ0pnXrhf7iuJ72ZrXCdVwGjQqTnfUaVGzjtMBGxFrQ8y8w@mail.gmail.com' \
    --to=davidfdzp@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