revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rpm <rpm@lists.bufferbloat.net>
Subject: [Rpm] rpm meeting notes from last week
Date: Sun, 27 Mar 2022 10:25:47 -0400	[thread overview]
Message-ID: <CAA93jw6r1ZxmrEjHbkP1D4wL7zA3ZgfrU8k8+oPpfTi=fQznRg@mail.gmail.com> (raw)

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.

-- 
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

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-27 14:25 Dave Taht [this message]
2022-03-27 14:41 ` Sebastian Moeller
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='CAA93jw6r1ZxmrEjHbkP1D4wL7zA3ZgfrU8k8+oPpfTi=fQznRg@mail.gmail.com' \
    --to=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