From: Dave Taht <dave.taht@gmail.com>
To: 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: [Starlink] misery metrics & consequences
Date: Fri, 21 Oct 2022 14:04:28 -0700 [thread overview]
Message-ID: <CAA93jw4w27a1EO_QQG7NNkih+C3QQde5=_7OqGeS9xy9nB6wkg@mail.gmail.com> (raw)
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
next reply other threads:[~2022-10-21 21:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 21:04 Dave Taht [this message]
2022-10-21 23:50 ` Dave Taht
2022-10-25 6:15 ` [Starlink] [Rpm] " Taraldsen Erik
2022-10-22 20:18 ` [Starlink] [M-Lab-Discuss] " rjmcmahon
2022-10-22 21:00 ` [Starlink] " Dave Collier-Brown
2022-10-22 22:18 ` Dave Taht
2022-10-23 0:17 ` [Starlink] [M-Lab-Discuss] " Glenn Fishbine
2022-10-23 11:57 ` [Starlink] [Rpm] " Sebastian Moeller
2022-10-23 12:17 ` Dave Collier-Brown
2022-10-23 12:26 ` Sebastian Moeller
2022-10-23 13:11 ` Dave Collier-Brown
2022-10-23 13:52 ` Sebastian Moeller
2022-10-23 14:00 ` Dave Collier-Brown
2022-10-23 14:08 ` Sebastian Moeller
2022-10-23 14:08 ` Dave Collier-Brown
2022-10-23 15:01 ` tom
2022-10-24 20:08 ` 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 ` [Starlink] [tsvwg] " Neal Cardwell
2022-10-25 15:17 ` [Starlink] [Rpm] [tsvwg] " rjmcmahon
2022-10-31 8:59 ` [Starlink] [ippm] [tsvwg] [Rpm] " Ruediger.Geib
2022-10-25 15:50 ` [Starlink] [ippm] " J Ignacio Alvarez-Hamelin
2022-10-26 8:14 ` [Starlink] [mat-wg] " Dave Taht
2022-10-25 16:07 ` [Starlink] " J Ignacio Alvarez-Hamelin
2022-10-25 17:02 ` [Starlink] [Rpm] [ippm] " rjmcmahon
2022-10-25 20:17 ` J Ignacio Alvarez-Hamelin
2022-10-24 17:37 ` [Starlink] " Dave Collier-Brown
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4w27a1EO_QQG7NNkih+C3QQde5=_7OqGeS9xy9nB6wkg@mail.gmail.com' \
--to=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