revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: "jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>
To: Rpm <rpm@lists.bufferbloat.net>
Subject: [Rpm] Changes to RPM calculation for MacOS Ventura?
Date: Fri, 28 Oct 2022 17:45:25 -0400	[thread overview]
Message-ID: <CE155801-683A-41AE-9ABC-8B5586319D3F@jonathanfoulkes.com> (raw)

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

Hopefully, Christoph can provide some details on the changes from the prior networkQuality test, as we’re seeing some pretty large changes in results for the latest RPM tests.

Where before we’d see results in the >1,500 RPM (and multiple >2,000 RPM results) for a DOCSIS 3.1 line with QoS enabled (180 down/35 up), it now returns peak download RPM of ~600 and ~800 for upload.

latest results:

==== SUMMARY ====
Uplink capacity: 25.480 Mbps (Accuracy: High)
Downlink capacity: 137.768 Mbps (Accuracy: High)
Uplink Responsiveness: Medium (385 RPM) (Accuracy: High)
Downlink Responsiveness: Medium (376 RPM) (Accuracy: High)
Idle Latency: 43.875 milli-seconds (Accuracy: High)
Interface: en8
Uplink bytes transferred: 35.015 MB
Downlink bytes transferred: 154.649 MB
Uplink Flow count: 16
Downlink Flow count: 12
Start: 10/28/22, 5:12:30 PM
End: 10/28/22, 5:12:54 PM
OS Version: Version 13.0 (Build 22A380)

Latencies (as monitored via PingPlotter) stay absolutely steady during these tests,

So unless my ISP coincidentally started having major service issues, I’m scratching my head as to why.

For contrast, the Ookla result is as follows: https://www.speedtest.net/result/13865976456  with 15ms down, 18ms up loaded latencies.

Further machine details: MacBook Pro 16” (2019) using a USB-C to Ethernet adapter.
I run with full ECN enabled:
sudo sysctl -w net.inet.tcp.disable_tcp_heuristics=1 

sudo sysctl -w net.inet.tcp.ecn_initiate_out=1

sudo sysctl -w net.inet.tcp.ecn_negotiate_in=1

and also with instant ack replies:

sysctl net.inet.tcp.delayed_ack
net.inet.tcp.delayed_ack: 0

I did try with delayed_ack=1, and the results were about the same.

Thanks in advance,

Jonathan Foulkes


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

             reply	other threads:[~2022-10-28 21:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 21:45 jf [this message]
2022-10-29 16:53 ` Sebastian Moeller
2022-11-01 21:52 ` Christoph Paasch
2022-11-01 22:09   ` Sebastian Moeller
2022-11-10 19:52     ` Christoph Paasch
2022-11-03 22:09   ` jf
2022-11-04 20:50     ` jf
2022-11-10 20:41       ` Christoph Paasch
2022-11-10 20:28     ` Christoph Paasch
2022-11-10 20:59       ` rjmcmahon

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=CE155801-683A-41AE-9ABC-8B5586319D3F@jonathanfoulkes.com \
    --to=jf@jonathanfoulkes.com \
    --cc=rpm@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