revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Matt Mathis <mattmathis@google.com>
To: Rpm <rpm@lists.bufferbloat.net>
Subject: [Rpm] First look at longitudinal RPM data
Date: Tue, 3 Aug 2021 08:38:55 -0700	[thread overview]
Message-ID: <CAH56bmCkB0YJaNWFkjouyR4U6hkCGNGhXaH9DadTP0b4OXmpTg@mail.gmail.com> (raw)

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

Somewhat limited in several ways, but still fascinating.

tl;dr fairly flat 2009 - 2016, and then 3x improvement over the last 5
years.

https://docs.google.com/document/d/1HkeJTgwLdbbdHe0dF9SWrpr8Vt7ngnovLpdDTScuUtk/

Dave, do you have a bufferbloat timeline?   Especially listing major
publications and PR events?

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

We must not tolerate intolerance;
       however our response must be carefully measured:
            too strong would be hypocritical and risks spiraling out of
control;
            too weak risks being mistaken for tacit approval.

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

                 reply	other threads:[~2021-08-03 15:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAH56bmCkB0YJaNWFkjouyR4U6hkCGNGhXaH9DadTP0b4OXmpTg@mail.gmail.com \
    --to=mattmathis@google.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