Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Nathan Owens <nathan@nathan.io>
To: "Gary E. Miller" <gem@rellim.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] GPS Dongle?
Date: Wed, 16 Jun 2021 20:04:04 -0700	[thread overview]
Message-ID: <CALjsLJuCyeYm2_O2LsTzvEDQgvOghM-mr10_hdHccYXOWDN1+A@mail.gmail.com> (raw)
In-Reply-To: <CALjsLJssnUA8ByOTb44W2D7yY=Dj-GBrAh3EhePeSUOOBQfmwQ@mail.gmail.com>

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

I should note this is very fresh and the jitter is dropping.

     remote           refid      st t when poll reach   delay   offset
 jitter
==============================================================================
o127.127.22.0    .PPS.            0 l    5   16  377    0.000    0.285
0.014

On Wed, Jun 16, 2021 at 8:00 PM Nathan Owens <nathan@nathan.io> wrote:

> Hey Gary,
>
> Got this running:
>
> pi@realtimepi:~ $ ntpq -crv -pn
> associd=0 status=0115 leap_none, sync_pps, 1 event, clock_sync,
> version="ntpd 4.2.8p12@1.3728-o (1)", processor="armv7l",
> system="Linux/4.19.71-rt24-v7l", leap=00, stratum=1, precision=-20,
> rootdelay=0.000, rootdisp=1.195, refid=PPS,
> reftime=e4753908.36ea5b4a  Wed, Jun 16 2021 19:59:20.214,
> clock=e4753915.668e763d  Wed, Jun 16 2021 19:59:33.400, peer=23018, tc=4,
> mintc=3, offset=0.298251, frequency=-22.915, sys_jitter=0.149930,
> clk_jitter=1.980, clk_wander=0.051
>
>      remote           refid      st t when poll reach   delay   offset
>  jitter
>
> ==============================================================================
> o127.127.22.0    .PPS.            0 l   13   16  377    0.000    0.298
> 0.150
> *216.239.35.12   .GOOG.           1 u   36   64  377   61.574   -4.184
>  24.605
>
> Let me know how it looks, or if there's anything I could improve!
>
> On Mon, Jun 14, 2021 at 1:38 PM Gary E. Miller <gem@rellim.com> wrote:
>
>> Yo Ricky!
>>
>> On Mon, 14 Jun 2021 13:25:26 -0700
>> Ricky Mok <cskpmok@caida.org> wrote:
>>
>> > Attached a paper on this topic from my old colleagues.
>>
>> Not bad.  It skipped the important details of how they configured their
>> RasPi's.  It also made the very common mistake of over smoothing their
>> ADEV measurements.  Lacking a few now standard metrics.  Otherwise
>> sound.
>>
>> It is possible to do a little better now.
>>
>> RGDS
>> GARY
>>
>> ---------------------------------------------------------------------------
>> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>>         gem@rellim.com  Tel:+1 541 382 8588
>>
>>             Veritas liberabit vos. -- Quid est veritas?
>>     "If you can't measure it, you can't improve it." - Lord Kelvin
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
>

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

  reply	other threads:[~2021-06-17  3:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 14:55 Nathan Owens
2021-06-14 17:40 ` Nathan Owens
2021-06-14 19:07   ` Gary E. Miller
2021-06-14 19:09     ` Nathan Owens
2021-06-14 19:13       ` Nathan Owens
2021-06-14 20:18         ` Gary E. Miller
2021-06-14 20:25           ` Ricky Mok
2021-06-14 20:38             ` Gary E. Miller
2021-06-17  3:00               ` Nathan Owens
2021-06-17  3:04                 ` Nathan Owens [this message]
2021-06-17  3:09                 ` Gary E. Miller
2021-06-17  3:11                   ` Nathan Owens
2021-06-17  3:15                     ` Gary E. Miller
2021-06-14 19:40       ` Gary E. Miller

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=CALjsLJuCyeYm2_O2LsTzvEDQgvOghM-mr10_hdHccYXOWDN1+A@mail.gmail.com \
    --to=nathan@nathan.io \
    --cc=gem@rellim.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