[Bloat] $106 achieved and flent-farm status

Tue Feb 5 04:37:43 EST 2019

> On Feb 5, 2019, at 4:37 AM, Dave Taht <dave.taht at gmail.com> wrote:
> 
> Thank you mikael and jake, matt and matthew and richard! (and jon, and
> dev for trying)

+1

> and here's a puzzler for you! Both boxes are running ntp yet one box
> was still *30* seconds off.

I haven’t explored this fully but I find it works best when ntp is configured in an identical way across servers, either all running systemd-timesyncd, or ntpd, or chronyd, and to the same server pool. When that’s the case, I often see it works within a few milliseconds.

For me, it looks like clocks are currently about 10ms off to london and 75ms off to singapore. I’m using systemd-timesyncd with the default Debian servers- "0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org”.

> irtt 1ms between california and germany has a mindboggling amount of
> loss... in america... ahh... tools…

Curiously, I see less loss at 1ms to singapore than london, london’s loss comes from the downstream, and I wasn’t seeing it four days ago. The upstream loss is my NLOS uplink as I get it straight to my next hop, which also has an irtt server.

Next hop router:
   packets sent/received: 4999/4864 (2.70% loss)
 server packets received: 4864/4999 (2.70%/0.00% loss up/down)

London:
   packets sent/received: 5000/4124 (17.52% loss)
 server packets received: 4817/5000 (3.66%/14.39% loss up/down)

Singapore:
   packets sent/received: 5000/4830 (3.40% loss)
 server packets received: 4830/5000 (3.40%/0.00% loss up/down)

Also curiously, RTT to london has increased for some reason, mainly with increased receive delay, but this could easily be from our peering provider, which we hope to switch soon for other reasons.

Feb. 1, 2019
------------

$ irtt client -q -i 10ms -d 1s flent-london.bufferbloat.net <http://flent-london.bufferbloat.net/>
[Connecting] connecting to flent-london.bufferbloat.net <http://flent-london.bufferbloat.net/>
[176.58.107.8:2112] [Connected] connection established
[176.58.107.8:2112] [WaitForPackets] waiting 135ms for final packets

                         Min     Mean   Median      Max  Stddev
                         ---     ----   ------      ---  ------
                RTT  31.08ms  37.09ms  37.04ms  44.98ms  2.75ms
         send delay  16.02ms  21.55ms  21.39ms  29.51ms  2.67ms
      receive delay   14.3ms  15.54ms  15.61ms   17.2ms   470µs

      IPDV (jitter)   49.5µs   3.27ms   2.45ms  10.85ms  2.88ms
          send IPDV   63.4µs   3.16ms   2.22ms  10.79ms  2.84ms
       receive IPDV    903ns    400µs    203µs   2.82ms   506µs

     send call time   21.3µs   79.1µs             146µs  28.9µs
        timer error   1.84µs    721µs            2.22ms   501µs
  server proc. time   1.29µs   31.4µs            2.23ms   222µs

                duration: 1.13s (wait 135ms)
   packets sent/received: 100/100 (0.00% loss)
 server packets received: 100/100 (0.00%/0.00% loss up/down)
     bytes sent/received: 6000/6000
       send/receive rate: 48.5 Kbps / 48.8 Kbps
           packet length: 60 bytes
             timer stats: 0/100 (0.00%) missed, 7.21% error

Feb. 5, 2019
------------

$ irtt client -q -i 10ms -d 1s flent-london.bufferbloat.net
[Connecting] connecting to flent-london.bufferbloat.net
[176.58.107.8:2112] [Connected] connection established
[176.58.107.8:2112] [WaitForPackets] waiting 176.8ms for final packets

                         Min     Mean   Median      Max  Stddev
                         ---     ----   ------      ---  ------
                RTT  53.38ms  54.59ms  54.38ms  58.93ms  1.05ms
         send delay  16.81ms  18.07ms  17.87ms  22.17ms   998µs
      receive delay  35.72ms  36.52ms   36.5ms  38.07ms   333µs

      IPDV (jitter)   47.1µs    960µs    370µs   4.69ms  1.03ms
          send IPDV   13.4µs    974µs    646µs   4.69ms  1.04ms
       receive IPDV   5.05µs    379µs    287µs   1.51ms   322µs

     send call time   32.5µs   35.5µs              61µs  3.65µs
        timer error     90ns   15.1µs             190µs  25.5µs
  server proc. time   7.47µs   13.4µs             191µs  20.6µs

                duration: 1.17s (wait 176.8ms)
   packets sent/received: 99/77 (22.22% loss)
 server packets received: 99/99 (0.00%/22.22% loss up/down)
     bytes sent/received: 5940/4620
       send/receive rate: 48.0 Kbps / 37.3 Kbps
           packet length: 60 bytes
             timer stats: 1/100 (1.00%) missed, 0.15% error

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20190205/24e66288/attachment-0002.html>