Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: tom@evslin.com
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Hello List
Date: Wed, 02 Mar 2022 14:55:26 -0500	[thread overview]
Message-ID: <22796.1646250926@localhost> (raw)
In-Reply-To: <20ba01d82e63$67eac9f0$37c05dd0$@evslin.com>

[-- Attachment #1: Type: text/plain, Size: 811 bytes --]


<tom@evslin.com> wrote:
    > need to prosper in the hybrid digital world. As all of you know, QoS is much
    > more than up and downlink speed and tough-to-quantify jitter is a huge part
    > of it. My measurement tool zoomready (at freecheckip.com
    > <http://freecheckip.com/>  and  https://github.com/tevslin/zoomready) makes
    > a more or less continuous measurement of jitter but is quite crude; so

I think that Apple/Stuart did a good job inverting the jitter metric, and calling it
Rounds/Revolutions per Minute.  I suggest doing the same in your tool.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 398 bytes --]

  reply	other threads:[~2022-03-02 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 18:29 tom
2022-03-02 19:55 ` Michael Richardson [this message]
2022-03-02 20:05   ` Dave Täht
2022-03-19 21:42     ` Omer Shapira

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=22796.1646250926@localhost \
    --to=mcr@sandelman.ca \
    --cc=starlink@lists.bufferbloat.net \
    --cc=tom@evslin.com \
    /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