General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] goresponsiveness learned a few tricks...
Date: Tue, 9 Jan 2024 08:18:20 +0100	[thread overview]
Message-ID: <523A469A-C87B-4EED-AD9F-D261723099F4@gmx.de> (raw)
In-Reply-To: <CAPDSy+6vhYX+rWyYLKontROsrUOT8rBouQYhLu9J3vjyby_NkQ@mail.gmail.com>

Hi David,


> On Jan 9, 2024, at 00:15, David Schinazi <dschinazi.ietf@gmail.com> wrote:
> 
> My understanding is that Apple chose to report RTT as an inverse because people are used to "higher number means better". The target audience for network speed tests is the average slightly-tech-savvy consumer, and those aren't all familiar with what latency means. Also, car enthusiasts like RPMs :-)

	Yes, I understand the rationale, I am just not buying it 100%. As I said people are well accustomed to values were "less is more" (prices, taxes, marathon times, ...) and I am not sure whether catering to the lowest common denominator is all that superior to teaching folks the relevant numbers... After all the trade-off is that now if people want to decompose or aggregate RPM values they need to deal with fractions... However for the responsiveness draft I fully accept that ship has sailed and "bigger is better" it is ;)


Regards
	Sebastian


> David
> 
> On Mon, Jan 8, 2024 at 1:53 PM Sebastian Moeller via Bloat <bloat@lists.bufferbloat.net> wrote:
> Hi Julien,
> 
> On 8 January 2024 22:04:23 CET, Juliusz Chroboczek <jch@irif.fr> wrote:
> >> (h++ps://github.com/network-quality/draft-ietf-ippm-responsiveness).
> >
> >There's quite a few good ideas in this draft, but the one that I find
> >intriguing is reporting RTT values in RPM (units of 1/60 Hz) rather than
> >milliseconds.
> 
> That idea, reporting the reciprocal has been around for some time, I think I first heard it from Jonathan Morton. But this is the first implementation....
> 
> Now personally I tend to think about 'latency' as sort of a budget, and then accounting where this budget is spent is easier with durations than periods. But I understand the attraction of 'bigger is better' numbers as well. Though most people also know smaller is better number, like product prices or taxes owed, but I digress.
> 
> 
> >
> >I wonder how well this works.  I'll experiment with undergrads.
> 
> The goresponsiveness code is quite readable and might give a convenient starting point for some quick and dirty exploration...
> 
> >
> >-- Juliusz
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


  reply	other threads:[~2024-01-09  7:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 19:41 Sebastian Moeller
2024-01-08 21:04 ` Juliusz Chroboczek
2024-01-08 21:53   ` Sebastian Moeller
2024-01-08 23:15     ` David Schinazi
2024-01-09  7:18       ` Sebastian Moeller [this message]
2024-01-09 14:05       ` Michael Richardson

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=523A469A-C87B-4EED-AD9F-D261723099F4@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dschinazi.ietf@gmail.com \
    --cc=jch@irif.fr \
    /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