revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Brennen Smith <brennen@ookla.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] LUL 220ms flat over starlink
Date: Tue, 2 Aug 2022 08:17:15 -0700	[thread overview]
Message-ID: <CAFwpvt7BeYr2ZEL+ZeqEJVDTHGykYY1ibnzGDD8pFD2TBHXw+w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6+vMwUcHw3ySG+uq3h1Kvj4m=xAUbG=pb6fyWcNjfXKA@mail.gmail.com>

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

Compared to GEO Sat links, this is very reasonable latency and distance.

Either GeoIP is wrong, or they’re starting to balance within the mesh for
capacity. If you look very closely at the maritime announcement - they’re
right on schedule for the latter.

On Tue, Aug 2, 2022 at 07:41 Dave Taht <dave.taht@gmail.com> wrote:

> It is my guess over a path this (inaccurately selected? lasered?)
> long, the new speedtest doesn't saturate the link.
>
> https://twitter.com/olegkutkov/status/1554404854763819008
>
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
>
-- 

Brennen Smith VP Technology

(206) 739-0807 | brennen@ookla.com

linkedin.com/in/brennensmith <https://www.linkedin.com/in/brennensmith/>

-- 


This email, its contents and attachments contain information from Ziff 
Davis, Inc. and/or its affiliates which may be privileged, confidential or 
otherwise protected from disclosure. The information is intended to be for 
the addressee(s) only. If you are not an addressee, any disclosure, copy, 
distribution or use of the contents of this message is prohibited. If you 
have received this email in error, please notify the sender by reply email 
and delete the original message and any copies.


[-- Attachment #2: Type: text/html, Size: 3140 bytes --]

  reply	other threads:[~2022-08-02 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 14:41 Dave Taht
2022-08-02 15:17 ` Brennen Smith [this message]
2022-08-02 15:25   ` [Rpm] [Starlink] " Mike Puchol
2022-08-03  8:42     ` Bjørn Ivar Teigen
2022-08-03  9:47       ` Sebastian Moeller

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/rpm.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFwpvt7BeYr2ZEL+ZeqEJVDTHGykYY1ibnzGDD8pFD2TBHXw+w@mail.gmail.com \
    --to=brennen@ookla.com \
    --cc=dave.taht@gmail.com \
    --cc=rpm@lists.bufferbloat.net \
    --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