From: Dave Taht <dave.taht@gmail.com>
To: Pedro Tumusok <pedro.tumusok@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
"dpreed@reed.com" <dpreed@reed.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Latency Measurements in Speed Test suites (was: DOCSIS 3+ recommendation?)
Date: Mon, 30 Mar 2015 07:55:03 -0700 [thread overview]
Message-ID: <CAA93jw7Jh2h+HAgFQ7dkkBx6o47_2DsWvz-C_09q-jVjg6Yu1g@mail.gmail.com> (raw)
In-Reply-To: <CACQiMXYZ+9jBNTc30-C-RNapn0mpcGVL0MKnvx=QjcR5Bon01g@mail.gmail.com>
I think the most effective thing would be to add bufferbloat testing
infrastructure to the web browsers themselves. There are already
plenty of tools for measuring web performance (whyslow for firefox,
the successor to chrome web page benchmarker) more or less built in...
measuring actual network performance under load is not much of a
reach.
The issues this would resolve are:
1) speed - the test(s) could use native apis within the browser and
thus achieve higher rates of speed than is possible with javascript
(and monitor cpu usage)
2) we could rigorously define the tests to have similar features to
netperf-wrapper
3) we could get much better tcp statistics as in with TCP_INFO
4) output formats could still be json as we do today, but plotted better
5) ?
Problems are:
0) Convincing users to use (and believe) them
1) Suitable server targets for the tests themselves
2) Although the browsers are basically in a nearly quarterly update
cycle, it would still take time for the tests to be widely available
even if they were ready today
3) Convincing the browser makers that they could use such tests
4) Writing the tests (in C and C++)
5) The outcry at speedtest, et al, for obsoleting their tools
(think microsoft vs "stacker")
6) Bloating up the browsers still further
next prev parent reply other threads:[~2015-03-30 14:55 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150316203532.05BD21E2@taggart.lackof.org>
[not found] ` <123130.1426635142@turing-police.cc.vt.edu>
[not found] ` <b8526a9c-5305-4467-8fd2-a6d1e0016903@reed.com>
[not found] ` <CAJq5cE2nLRKuq64vQgpPSQ01e2Mc5Vtguo6smQg+ySC8mLH=aQ@mail.gmail.com>
[not found] ` <15A0911A-E3B7-440A-A26B-C5E1489EA98B@viagenie.ca>
[not found] ` <CAJq5cE1UFgt6fpLxRH7m3VFUpziGZm9OLCCNFQ93QemH00CHaQ@mail.gmail.com>
[not found] ` <1426773234.362612992@apps.rackspace.com>
2015-03-19 17:11 ` [Bloat] [Cerowrt-devel] DOCSIS 3+ recommendation? Dave Taht
2015-03-19 19:58 ` Livingood, Jason
2015-03-19 20:29 ` dpreed
2015-03-19 23:18 ` Greg White
2015-03-20 8:18 ` MUSCARIELLO Luca IMT/OLN
2015-03-20 13:31 ` David P. Reed
2015-03-20 13:46 ` Sebastian Moeller
2015-03-20 14:05 ` MUSCARIELLO Luca IMT/OLN
2015-03-20 10:07 ` Sebastian Moeller
2015-03-20 13:50 ` [Bloat] Latency Measurements in Speed Test suites (was: DOCSIS 3+ recommendation?) Rich Brown
2015-03-29 17:36 ` Pedro Tumusok
2015-03-30 7:06 ` Jonathan Morton
2015-03-30 13:56 ` Pedro Tumusok
2015-03-30 14:18 ` Jonathan Morton
2015-03-30 14:20 ` Pedro Tumusok
2015-03-30 14:55 ` Dave Taht [this message]
2015-03-30 16:05 ` Pedro Tumusok
2015-03-31 5:07 ` Jesper Dangaard Brouer
2015-04-01 17:21 ` Pedro Tumusok
[not found] ` <CAH3Ss96599p_22c+9Dm5s2LUGwkvnc_ivunpz6aTzDAteS1ZPg@mail.gmail.com>
[not found] ` <CACQiMXYxbbLh=rVWK2MnTfo7xePoy794k_V36XDrJxybKiiC9g@mail.gmail.com>
2015-04-07 17:16 ` [Bloat] Fwd: " Pedro Tumusok
2015-03-30 16:20 ` [Bloat] " Livingood, Jason
2015-03-31 1:30 ` Pedro Tumusok
2015-03-31 4:14 ` Jonathan Morton
2015-03-30 14:42 ` [Bloat] Latency Measurements in Speed Test suites Toke Høiland-Jørgensen
2015-03-20 13:57 ` [Bloat] [Cerowrt-devel] DOCSIS 3+ recommendation? Livingood, Jason
2015-03-20 14:08 ` David P. Reed
2015-03-20 14:14 ` MUSCARIELLO Luca IMT/OLN
2015-03-20 14:48 ` Matt Mathis
2015-03-20 13:48 ` Jim Gettys
2015-03-20 14:11 ` Livingood, Jason
2015-03-20 14:54 ` Michael Welzl
2015-03-20 15:31 ` Jim Gettys
2015-03-20 15:39 ` Michael Welzl
2015-03-20 16:31 ` Jonathan Morton
2015-03-20 20:59 ` Michael Welzl
2015-03-20 23:47 ` David P. Reed
2015-03-21 0:08 ` Michael Welzl
2015-03-21 0:03 ` David Lang
2015-03-21 0:13 ` Steinar H. Gunderson
2015-03-21 0:25 ` David Lang
2015-03-21 0:34 ` Jonathan Morton
2015-03-21 0:38 ` David Lang
2015-03-21 0:43 ` Jonathan Morton
2015-03-22 4:15 ` Michael Welzl
2015-03-21 0:15 ` Michael Welzl
2015-03-21 0:29 ` David Lang
2015-03-22 4:10 ` Michael Welzl
2015-03-20 18:14 ` Jonathan Morton
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7Jh2h+HAgFQ7dkkBx6o47_2DsWvz-C_09q-jVjg6Yu1g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dpreed@reed.com \
--cc=pedro.tumusok@gmail.com \
/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