From: Michael Richardson <mcr@sandelman.ca>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Matt Mathis <mattmathis@google.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Credit and/or collaboration on a responsiveness metric?
Date: Tue, 06 Jul 2021 10:46:19 -0400 [thread overview]
Message-ID: <25880.1625582779@localhost> (raw)
In-Reply-To: <5C8DA517-01DE-477F-9B3D-952D953EEC89@gmail.com>
Jonathan Morton <chromatix99@gmail.com> wrote:
> My idea was simply to express delays and latencies as a frequency, in
> Hz, so that "bigger numbers are better", rather than always in
> milliseconds, where "smaller numbers are better". The advantage of Hz
> is that you can directly compare it to framerates of video or
> gameplay.
Marketing people will get this better.
They already know that higher-Mhz is better :-)
next prev parent reply other threads:[~2021-07-06 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 23:21 Matt Mathis
2021-07-06 0:09 ` Dave Taht
2021-07-06 8:48 ` Jonathan Morton
2021-07-06 14:46 ` Michael Richardson [this message]
2021-07-07 8:00 ` Sebastian Moeller
2021-07-06 19:04 ` Matt Mathis
2021-07-06 21:56 ` Kathleen Nichols
2021-07-06 16:28 ` Christoph Paasch
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=25880.1625582779@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=mattmathis@google.com \
/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