From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: dave.collier-brown@indexexchange.com,
Dave Taht <dave.taht@gmail.com>,
David Collier-Brown <davecb@spamcop.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE?
Date: Mon, 07 Sep 2020 11:23:14 +0200 [thread overview]
Message-ID: <87k0x6os8t.fsf@toke.dk> (raw)
In-Reply-To: <c1ffb3fb-0802-a96d-1c58-0d55723e76de@indexexchange.com>
Dave Collier-Brown <dave.collier-brown@indexexchange.com> writes:
> LWN said OK, but I'm stuck on the search for a striking test, one that resonates with "grandma".
>
> My next two thoughts, probably for the current long weekend, is either
> to call a loop-back number with Skype and/or ask Toke how he got "Big
> Buck Bunny" to suffer dropouts. I'd love to use the latter, as it
> aligns with the observation that this is a time when conference-call
> failures are driving my colleagues to drink (;-))
I assume you're referring to the Dash data included in the Polify paper,
right? :)
Not sure if I ever got it to drop out completely; just did some
measurements of which bitrate it picked, and the context was airtime
prioritisation, not so much the latency improvements. But anyway, the
tests just used the reference dash.js[0] player, with a logger addition
that Flent can parse[1].
I don't recall what exactly is needed on the server side to run this,
but I think it's basically just dropping the right Big Buck Bunny
tarball on a web server along with dash-logger.js from the Flent sources :)
-Toke
[0] https://github.com/Dash-Industry-Forum/dash.js/wiki
[1] https://github.com/tohojo/flent/commit/6b83896cc0df1d468577ef0f35abbab6dd025c3f
next prev parent reply other threads:[~2020-09-07 9:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 18:27 David Collier-Brown
2020-08-09 19:18 ` Tom Henderson
2020-08-09 21:35 ` Jonathan Morton
2020-08-10 12:57 ` David Collier-Brown
2020-08-10 14:00 ` Daniel Sterling
2020-08-10 15:08 ` Tom Henderson
2020-08-10 15:34 ` Sebastian Moeller
2020-08-10 15:57 ` Jonathan Morton
2020-08-10 16:04 ` Tom Henderson
2020-08-11 12:43 ` Daniel Sterling
2020-08-11 13:57 ` Kenneth Porter
[not found] ` <D8B6D86243E4539BBA58E32C@172.27.17.193>
2020-08-11 14:09 ` Daniel Sterling
2020-08-11 14:11 ` Daniel Sterling
2020-08-11 16:19 ` Kenneth Porter
2020-08-10 17:58 ` Jonathan Foulkes
2020-08-10 19:13 ` Carlos R. Pasqualini
2020-08-10 20:28 ` Dave Collier-Brown
2020-08-11 12:41 ` Michael Yartys
2020-08-10 14:16 ` [Bloat] Sidebar to "How about a topical LWN article on demonstrating the real-world goodness of CAKE?" David Collier-Brown
2020-08-11 15:48 ` [Bloat] How about a topical LWN article on demonstrating the real-world goodness of CAKE? Simon Barber
2020-09-05 18:52 ` Dave Taht
2020-09-05 20:35 ` Dave Collier-Brown
2020-09-07 9:23 ` Toke Høiland-Jørgensen [this message]
2020-09-07 11:33 ` Dave Collier-Brown
2020-09-07 17:20 ` David Collier-Brown
2020-09-08 15:43 ` Dave Taht
2020-09-08 16:48 ` Matt Mathis
2020-09-08 17:09 ` Jonathan Morton
2020-09-10 15:08 ` Anthony Minessale II
2020-09-10 16:52 ` 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/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=87k0x6os8t.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.collier-brown@indexexchange.com \
--cc=dave.taht@gmail.com \
--cc=davecb@spamcop.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