revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Christoph Paasch <cpaasch@apple.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] the de-evolution of rpm
Date: Fri, 14 Apr 2023 13:15:19 -0700	[thread overview]
Message-ID: <FA231E88-4F33-4C57-A0E7-D84782175D6F@apple.com> (raw)
In-Reply-To: <CAA93jw7ohF3ep4XfgRJecCqD-hT0H58em=76+ho_=p8ayhHY3A@mail.gmail.com>

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

Hello Dave,

> On Apr 13, 2023, at 3:13 PM, Dave Taht via Rpm <rpm@lists.bufferbloat.net> wrote:
> 
> I have not been paying a lot of attention here of late. I objected to
> the enormous number of flows goresponsiveness was doing, and strongly
> suggested it run to time of first loss or mark.
> I find 4 flows enough
> to stress out a network.

4 flows should often be enough to utilize a network at its full capacity. However, are 4 flows going to provide you stable working conditions in such a way that the bottleneck’s buffers are entirely full over an extended period without fluctuations due to the congestion-response of the individual flows? Also, what is the convergence time to reach stable working conditions and full buffer utilization at 4 flows?

Now, that being said. I don’t think that the exact number of flows is that important. They just need to be enough to fill the buffers in a stable way. All nit-picking on the number of flows just distracts us from actually solving problems on the Internet.

> Anyway, is the structure of networkQuality
> changing any in ippm?

Yes, the IETF-draft is continuously evolving. You can read the latest version at https://datatracker.ietf.org/doc/html/draft-ietf-ippm-responsiveness.

Discussions around the methodology and the development of the tools as well as addressing issues we find in open-source networking stacks is all happening at the “Network-quality community”, at https://github.com/network-quality/community/wiki. We have a slack-channel and a weekly meeting. Everyone who is actively working on development is invited to join our slack-channel and attend the weekly meetings. (The "active development" is a strong requirement )


Cheers,
Christoph

> Some context here:
> 
> https://www.reddit.com/r/amazoneero/comments/12ksu9d/sqm_optimizing_for_videoconferencing_and_gaming/jg4zsq2/?context=8&depth=9
> 
> 
> -- 
> AMA March 31: https://www.broadband.io/c/broadband-grant-events/dave-taht
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm


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

  reply	other threads:[~2023-04-14 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 22:13 Dave Taht
2023-04-14 20:15 ` Christoph Paasch [this message]
2023-04-14 21:02   ` Dave Taht
2023-04-14 21:17     ` Christoph Paasch
2023-04-14 21:26       ` [Rpm] Vote: Closing the rpm list? Dave Taht
2023-04-15  0:03         ` Frantisek Borsik
2023-04-15  0:18           ` Dave Taht
2023-04-15  0:29             ` JAMES R CUTLER

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=FA231E88-4F33-4C57-A0E7-D84782175D6F@apple.com \
    --to=cpaasch@apple.com \
    --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