revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: rpm@lists.bufferbloat.net
Subject: [Rpm] Alternate definitions of "working condition" - unnecessary?
Date: Wed, 6 Oct 2021 15:11:53 -0400	[thread overview]
Message-ID: <E874E0D0-31B6-4F0D-8844-83A3B317F2B1@gmail.com> (raw)

A portion of yesterday's RPM call encouraged people to come up with new definitions of "working conditions".

This feels like a red herring. 

We already have two worst-case definitions - with implementations - of tools that "stuff up" a network. Flent and Apple's RPM Tool drive a network into worst-case behavior for long (> 60 seconds) and medium (~20 seconds) terms.

What new information would another "working conditions" test expose that doesn't already come from Flent/RPM Tool? Thanks.

Rich

             reply	other threads:[~2021-10-06 19:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 19:11 Rich Brown [this message]
2021-10-06 20:36 ` Jonathan Foulkes
2021-10-07 16:40   ` Toke Høiland-Jørgensen
2021-10-07 18:49     ` Dave Taht
2021-10-08 17:51       ` Toke Høiland-Jørgensen
2021-10-07 21:39   ` Rich Brown
2021-10-06 21:22 ` Dave Taht
2021-10-06 23:18   ` Jonathan Morton
2021-10-07  0:11     ` Christoph Paasch
2021-10-07 10:29       ` Jonathan Morton
2021-10-07 15:44         ` [Rpm] apple's fq_"codel" implementation Dave Taht
2021-10-07 10:30       ` [Rpm] Alternate definitions of "working condition" - unnecessary? Sebastian Moeller
2021-10-08  0:33         ` Jonathan Morton
2021-10-08 23:32         ` Christoph Paasch
2021-10-11  7:31           ` Sebastian Moeller
2021-10-11  9:01             ` Jonathan Morton
2021-10-11 10:03               ` Sebastian Moeller
2021-10-11 17:34             ` Christoph Paasch
2021-10-12 10:23               ` Sebastian Moeller

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=E874E0D0-31B6-4F0D-8844-83A3B317F2B1@gmail.com \
    --to=richb.hanover@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