General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Matt Mathis <mattmathis@google.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Apple WWDC Talks on Latency/Bufferbloat
Date: Thu, 17 Jun 2021 11:16:34 -0700	[thread overview]
Message-ID: <CAH56bmAE=CzRjjMcJJHw53Rh_+cyWLvOZSyxN7RY36ZJcQWdCA@mail.gmail.com> (raw)
In-Reply-To: <62E013CF-ECE9-4022-B092-DFCE2176F772@gmail.com>

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

Is there a paper or spec for RPM?

There are at least two different ways to define RPM, both of which might be
relevant.

At the TCP layer: it can be directly computed from a packet capture.  The
trick is to time reverse a trace and compute the critical path backwards
through the trace: what event triggered each segment or ACK, and count
round trips.  This would be super robust but does not include the queueing
required in the kernel socket buffers.  I need to think some more about
computing TCP RPM from tcp_info or other kernel instrumentation - it might
be possible.

A different RPM can be done in the application, above TCP, for example by
ping-ponging messages.  This would include the delays traversing the kernel
socket buffers which have to be at least as large as a full network RTT.

This is perhaps an important point: due to the retransmit and
reassuebly queues (which are required to implement robust data delivery)
TCP must be able hold at least a full RTT of data in it's own buffers,
which means that under some conditions the RTT as seen by the application
has be be at least twice the network's RTT, including any bloat in the
network.

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

We must not tolerate intolerance;
       however our response must be carefully measured:
            too strong would be hypocritical and risks spiraling out of
control;
            too weak risks being mistaken for tacit approval.


On Sat, Jun 12, 2021 at 9:11 AM Rich Brown <richb.hanover@gmail.com> wrote:

> > On Jun 12, 2021, at 12:00 PM, bloat-request@lists.bufferbloat.net wrote:
> >
> > Some relevant talks / publicity at WWDC -- the first mentioning CoDel,
> > queueing, etc. Featuring Stuart Cheshire. iOS 15 adds a developer test
> for
> > loaded latency, reported in "RPM" or round-trips per minute.
> >
> > I ran it on my machine:
> > nowens@mac1015 ~ % /usr/bin/networkQuality
> > ==== SUMMARY ====
> > Upload capacity: 90.867 Mbps
> > Download capacity: 93.616 Mbps
> > Upload flows: 16
> > Download flows: 20
> > Responsiveness: Medium (840 RPM)
>
> Does anyone know how to get the command-line version for current (not
> upcoming) macOS? Thanks.
>
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

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

  reply	other threads:[~2021-06-17 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12 16:11 Rich Brown
2021-06-17 18:16 ` Matt Mathis [this message]
2021-06-17 23:43   ` Christoph Paasch
2021-06-18  0:17     ` Matt Mathis
2021-06-18  1:03       ` Christoph Paasch
2021-06-18  3:33         ` Matt Mathis
2021-06-28 22:54           ` Christoph Paasch
2021-06-29  7:58     ` Sebastian Moeller
2021-07-06 18:54       ` Christoph Paasch
2021-07-06 19:08         ` Sebastian Moeller
  -- strict thread matches above, loose matches on Subject: below --
2021-06-11 19:14 Nathan Owens
2021-06-11 21:58 ` Jonathan Morton

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

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

  git send-email \
    --in-reply-to='CAH56bmAE=CzRjjMcJJHw53Rh_+cyWLvOZSyxN7RY36ZJcQWdCA@mail.gmail.com' \
    --to=mattmathis@google.com \
    --cc=bloat@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