Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Recomended HW to run cake and fq_codel?
Date: Mon, 27 Nov 2017 13:47:53 +0100	[thread overview]
Message-ID: <53AFD81B-F9F5-4DE1-A418-A177D0F339E8@gmail.com> (raw)
In-Reply-To: <CAJq5cE0WNBxMvcXuybB5G6yEOEq0Z0ST7fhS_-y7SkfO7yVtMw@mail.gmail.com>

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


> On Nov 27, 2017, at 1:04 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
> My pet suggestion here is to represent latency as its inverse, "responsiveness" with units of Hz.  This has the dual advantages of bigger numbers being better, and the figures being directly comparable with framerates.
> 
> As you say, the methodology will need to be very carefully specified, so that we get a meaningful measurement that's hard to game.
> 
I like that idea...

Then it’s how to measure it. 1 / latency where latency is what…the maximum value you’ll see considering all traffic as besteffort at a fixed number of concurrent flows? Otherwise it would have do be expressed differently for different traffic classes, which is probably already too complicated for most people.

Food for thought, I know this is the opposite direction, but I’ve always liked in Europe how car “mileage” is expressed as consumption (L/100km) instead of efficiency (miles/gallon). Yes, then a lower number is better, but it’s easier to calculate how much gas you’ll use for a given trip.

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

  reply	other threads:[~2017-11-27 12:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1493740801.18318.cake@lists.bufferbloat.net>
2017-05-02 18:44 ` Pete Heist
2017-05-03  5:59   ` erik.taraldsen
2017-05-03  7:15     ` Pete Heist
2017-05-03 10:03       ` Andy Furniss
2017-05-03 11:10       ` erik.taraldsen
2017-11-27  8:35     ` Dave Taht
2017-11-27 12:04       ` Jonathan Morton
2017-11-27 12:47         ` Pete Heist [this message]
2017-11-27 15:54           ` Sebastian Moeller
2017-11-27 16:12             ` Pete Heist
2017-11-27 18:28               ` Jonathan Morton
2017-11-27 21:49                 ` Pete Heist
2017-11-28 18:15                   ` [Cake] Simple metrics Dave Taht
2017-11-28 22:14                     ` Pete Heist
2017-11-28 22:41                       ` Dave Taht
2017-11-29  8:08                         ` Sebastian Moeller
     [not found] <mailman.1.1493827201.27042.cake@lists.bufferbloat.net>
2017-05-03 18:05 ` [Cake] Recomended HW to run cake and fq_codel? Pete Heist
     [not found] <mailman.430.1493386395.3609.cake@lists.bufferbloat.net>
2017-04-28 16:39 ` Lochnair
2017-05-02 10:34   ` erik.taraldsen
2017-05-02 12:11     ` Nils Andreas Svee
2017-05-02 17:36       ` David Lang
2017-05-03  5:36       ` erik.taraldsen
2017-05-03  6:51         ` Sebastian Moeller
2017-05-03  7:27           ` erik.taraldsen
2017-05-03  8:24             ` Sebastian Moeller
2017-05-03 11:14               ` erik.taraldsen
     [not found] ` <mailman.433.1493397541.3609.cake@lists.bufferbloat.net>
2017-04-28 18:07   ` Tristan Seligmann

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53AFD81B-F9F5-4DE1-A418-A177D0F339E8@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dave.taht@gmail.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