From: Michael Richardson <mcr@sandelman.ca>
To: Cake List <cake@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] dslreports is no longer free
Date: Fri, 01 May 2020 19:59:07 -0400 [thread overview]
Message-ID: <17660.1588377547@localhost> (raw)
In-Reply-To: <mailman.191.1588369068.24343.bloat@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
Given QUIC uses UDP and does congestion control essentially within the
browser, it seems that maybe one could built latency under load measuring
into the QUIC infrastructure in the browser.
Maybe we don't have to create JS tools like fast.com to get good and
regular measurements of bufferbloat. Maybe it could be a part of
browsers. Maybe web site designers could ask for the current
"latency-under-load" value from the browser DOM.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-05-01 23:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 16:44 [Cake] " Dave Taht
2020-05-01 19:34 ` [Cake] [Bloat] " Kenneth Porter
2020-05-01 19:54 ` Sebastian Moeller
2020-05-01 19:48 ` [Cake] " Sebastian Moeller
2020-05-01 20:09 ` [Bloat] " Sergey Fedorov
2020-05-01 21:11 ` [Cake] [Bloat] " Sebastian Moeller
2020-05-01 21:37 ` [Bloat] [Cake] " Sergey Fedorov
[not found] ` <mailman.191.1588369068.24343.bloat@lists.bufferbloat.net>
2020-05-01 23:59 ` Michael Richardson [this message]
[not found] ` <mailman.170.1588363787.24343.bloat@lists.bufferbloat.net>
2020-05-01 22:07 ` [Cake] [Bloat] " Michael Richardson
2020-05-01 23:35 ` [Bloat] [Cake] " Sergey Fedorov
2020-05-02 1:14 ` [Cake] [Make-wifi-fast] [Bloat] " Jannie Hanekom
2020-05-02 16:37 ` Benjamin Cronce
2020-05-02 16:52 ` Dave Taht
2020-05-02 17:38 ` David P. Reed
2020-05-02 19:00 ` Sergey Fedorov
2020-05-02 23:23 ` David P. Reed
2020-05-03 15:31 ` [Cake] fast.com quality David P. Reed
2020-05-03 15:37 ` Dave Taht
2020-05-02 20:19 ` [Cake] [Make-wifi-fast] [Bloat] dslreports is no longer free Sebastian Moeller
2020-05-27 9:08 ` [Cake] " Matthew Ford
2020-05-27 9:28 ` [Cake] [Make-wifi-fast] " Toke Høiland-Jørgensen
2020-05-27 9:32 ` [Cake] " Sebastian Moeller
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=17660.1588377547@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@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