From: Glenn Fishbine <glenn@breakingpointsolutions.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>,
Measurement Analysis and Tools Working Group <mat-wg@ripe.net>,
IETF IPPM WG <ippm@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>,
discuss <discuss@measurementlab.net>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Rpm] [M-Lab-Discuss] misery metrics & consequences
Date: Sat, 22 Oct 2022 19:17:48 -0500 [thread overview]
Message-ID: <CABs+J_DhaLPp8nba=hqrg6Z_Db3DBH1__FymBsqEXgSDo+8-5w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4w27a1EO_QQG7NNkih+C3QQde5=_7OqGeS9xy9nB6wkg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2767 bytes --]
As a classic died in the wool empiricist, granted that you can identify
"misery" factors, given a population of 1,000 users, how do you propose
deriving a misery index for that population?
We can measure download, upload, ping, jitter pretty much without user
intervention. For the measurements you hypothesize, how you you
automatically extract those indecies without subjective user contamination.
I.e. my download speed sucks. Measure the download speed.
My isp doesn't fix my problem. Measure what? How?
Human survey technology is 70+ years old and it still has problems figuring
out how to correlate opinion with fact.
Without an objective measurement scheme that doesn't require human
interaction, the misery index is a cool hypothesis with no way to link to
actual data. What objective measurements can be made? Answer that and the
index becomes useful. Otherwise it's just consumer whining.
Not trying to be combative here, in fact I like the concept you support,
but I'm hard pressed to see how the concept can lead to data, and the data
lead to policy proposals.
On Fri, Oct 21, 2022, 5:20 PM Dave Taht <dave.taht@gmail.com> wrote:
> One of the best talks I've ever seen on how to measure customer
> satisfaction properly just went up after the P99 Conference.
>
> It's called Misery Metrics.
>
> After going through a deep dive as to why and how we think and act on
> percentiles, bins, and other statistical methods as to how we use the
> web and internet are *so wrong* (well worth watching and thinking
> about if you are relying on or creating network metrics today), it
> then points to the real metrics that matter to users and the ultimate
> success of an internet business: Timeouts, retries, misses, failed
> queries, angry phone calls, abandoned shopping carts and loss of
> engagement.
>
> https://www.p99conf.io/session/misery-metrics-consequences/
>
> The ending advice was - don't aim to make a specific percentile
> acceptable, aim for an acceptable % of misery.
>
> I enjoyed the p99 conference more than any conference I've attended in
> years.
>
> --
> This song goes out to all the folk that thought Stadia would work:
>
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
>
> --
> You received this message because you are subscribed to the Google Groups
> "discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to discuss+unsubscribe@measurementlab.net.
> To view this discussion on the web visit
> https://groups.google.com/a/measurementlab.net/d/msgid/discuss/CAA93jw4w27a1EO_QQG7NNkih%2BC3QQde5%3D_7OqGeS9xy9nB6wkg%40mail.gmail.com
> .
>
[-- Attachment #2: Type: text/html, Size: 3959 bytes --]
next prev parent reply other threads:[~2022-10-23 0:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 21:04 [Rpm] " Dave Taht
2022-10-21 23:50 ` Dave Taht
2022-10-25 6:15 ` Taraldsen Erik
2022-10-22 20:18 ` [Rpm] [M-Lab-Discuss] " rjmcmahon
2022-10-23 0:17 ` Glenn Fishbine [this message]
2022-10-23 11:57 ` Sebastian Moeller
2022-10-24 20:08 ` [Rpm] [Starlink] " Christoph Paasch
2022-10-24 20:57 ` Sebastian Moeller
2022-10-24 23:44 ` Christoph Paasch
2022-10-25 0:08 ` rjmcmahon
2022-10-25 0:12 ` rjmcmahon
2022-10-25 2:28 ` [Rpm] [tsvwg] " Neal Cardwell
2022-10-25 15:17 ` rjmcmahon
2022-10-25 16:07 ` [Rpm] [ippm] " J Ignacio Alvarez-Hamelin
2022-10-25 17:02 ` rjmcmahon
2022-10-25 20:17 ` J Ignacio Alvarez-Hamelin
[not found] ` <F290B086-FDDC-4C9E-AD46-3BAC446BD8C4@cnet.fi.uba.ar>
2022-10-26 8:14 ` [Rpm] [mat-wg] " Dave Taht
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='CABs+J_DhaLPp8nba=hqrg6Z_Db3DBH1__FymBsqEXgSDo+8-5w@mail.gmail.com' \
--to=glenn@breakingpointsolutions.com \
--cc=dave.taht@gmail.com \
--cc=discuss@measurementlab.net \
--cc=ippm@ietf.org \
--cc=mat-wg@ripe.net \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@lists.bufferbloat.net \
--cc=tsvwg@ietf.org \
/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