revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] rpm meeting notes from last week
Date: Sun, 27 Mar 2022 16:41:39 +0200	[thread overview]
Message-ID: <285BE48F-7C91-467E-B2CC-D0CAA575D529@gmx.de> (raw)
In-Reply-To: <CAA93jw6r1ZxmrEjHbkP1D4wL7zA3ZgfrU8k8+oPpfTi=fQznRg@mail.gmail.com>

Hi Dave,


> On Mar 27, 2022, at 16:25, Dave Taht via Rpm <rpm@lists.bufferbloat.net> wrote:
> 
> Sasha has re-organized the meeting notes we've been taking which will
> be permanently up here:
> 
> https://docs.google.com/document/d/19K14vrBLNvX_KOdRMK_s0SCYTnj70IJ-dQubL37kQgw/edit
> 
> The public meetings continue at 10AM PDT tuesdays.
> 
> One thing came up in that meeting that bears further reflection: The
> structure of the the responsiveness test is e2e, and differentiating
> between the wifi hop and/or sourcing tests from the router - is hard.
> In the latter case, we are asking a router not only to saturate its
> network connection, but to do it using crypto, which is a mighty task
> to ask of a router that's job is primarily routing (with offloads).
> 
> A thought might be to attempt p2p tests between say, an ios phone and
> an osx laptop, which would exercise the router as a wifi router. A
> docker container for the server would be straightforward. (It's still
> hard for me to
> trust containers or vm's to run fast or accurately enough, too).
> 
> Former case is still e2e but with the icmp unreachable idea I described in wtbb.

	IIRC a number of devices, especially those that would employ hardware assists for routing/forwarding will punt ICMP processing to slow-paths unto their (slowish) CPU, so extracting RTTs from ICMP responses of such nodes will include an additional source of variance/delay... that said, IIUC TTL-games is exactly what MTR does and it mostly seems to work (albeit with the occasional un-interpretable node). So it might make sense to at least try to RTT probe the whole path?

Regards
	Sebastian


> 
> -- 
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
> 
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm


  reply	other threads:[~2022-03-27 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-27 14:25 Dave Taht
2022-03-27 14:41 ` Sebastian Moeller [this message]
2022-03-27 18:34 ` Sebastian Moeller
2022-03-27 22:26   ` Will Hawkins
2022-03-28  7:58     ` Sebastian Moeller
2022-03-28  8:41       ` Sebastian Moeller
2022-03-28 16:56         ` Will Hawkins

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=285BE48F-7C91-467E-B2CC-D0CAA575D529@gmx.de \
    --to=moeller0@gmx.de \
    --cc=dave.taht@gmail.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