Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] NZ latest latency report
Date: Thu, 6 Jul 2023 10:20:41 +0200	[thread overview]
Message-ID: <CAC=tZ0rPdZYgecP18LbWUwzk9QTNSnmYmFx4HmuR-SsJq3=38w@mail.gmail.com> (raw)

I think they could recommend the RSP to provide better devices, but
SamKnows should then provide Whiteboxes that replace the device
provided by the RSP, to demonstrate that it can be done better, and
then compare the measurements with the original device provided by the
RSP vs. the better ones.

Tables 3, 4 and 5 in the report (starting at page 37) give some
latency measurements to different servers by Retail Service Provider
(RSP).

I have not seen specified in the report the duration of the
measurement tests. Why do you suspect the test is not running long
enough? What should be the duration of the tests?

They are reporting the average value for measurements and the range
where 95% of measurements fall, leaving out of the range the 2.5%
lower measurements and the 2.5% higher, I understand. What does they
"should be pulling from higher than what appears to be the 75th
percentile" mean?

Regards,

David

> Date: Wed, 5 Jul 2023 07:08:14 -0600
> From: Dave Taht <dave.taht@gmail.com>
> To: libreqos <libreqos@lists.bufferbloat.net>, Rpm
> 	<rpm@lists.bufferbloat.net>, Dave Taht via Starlink
> 	<starlink@lists.bufferbloat.net>
> Cc: Sam Crawford <sam@samknows.com>
> Subject: [Starlink] NZ latest latency report
> Message-ID:
> 	<CAA93jw6A9g4F8z5dUTnv_4oj2wRNWmEmxeRPX=DfDGaCF3jSwg@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> I do wish that it broke it out by provider, and recommended somehow to
> those suffering still, install a better device... VDSL can be made
> vastly more tolerable. Otherwise pretty good, and brings in
> starlink...
>
> https://comcom.govt.nz/__data/assets/pdf_file/0016/320326/MBNZ-Autumn-Report-28-June-2023.pdf
>
> To pick on samknows a little bit, I think the test does not run long
> enough, and should be pulling from higher than what appears to be the
> 75th percentile.
>
>
>
> --
> Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
> Dave Täht CSO, LibreQos

             reply	other threads:[~2023-07-06  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  8:20 David Fernández [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-05 13:08 Dave Taht
2023-07-05 21:17 ` Ulrich Speidel

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=tZ0rPdZYgecP18LbWUwzk9QTNSnmYmFx4HmuR-SsJq3=38w@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