From: Dave Taht <dave.taht@gmail.com>
To: Rpm <rpm@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Rpm] good latency metrics from jim roskind
Date: Tue, 20 Dec 2022 18:00:52 -0800 [thread overview]
Message-ID: <CAA93jw5w5HyJ+m49oMYwDT-95s9iMxsVh97tZQ1t7yur=vByfA@mail.gmail.com> (raw)
Good talk:
https://www.youtube.com/watch?v=_uaaCiyJCFA
What he had to say about fenceposts above really resonated with me. We
do 'round here, keep aiming for less and less latency, but a lot of
folk have settled on what is good enough by their lights. The p50 and
p90 animation
was brilliant AND hilarious...
Very high energy talk on QUIC's design decisions including a great
slide on the packet pacing experiment he did back in 2012 or 2013 or
so, also:
https://www.linkedin.com/feed/update/urn:li:activity:7011133658166157312/
--
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
reply other threads:[~2022-12-21 2:01 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='CAA93jw5w5HyJ+m49oMYwDT-95s9iMxsVh97tZQ1t7yur=vByfA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@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