From: "Francini, Andrea (Nokia - US)" <andrea.francini@nokia-bell-labs.com>
To: Dave Taht <dave.taht@gmail.com>,
bloat <bloat@lists.bufferbloat.net>,
"aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [Bloat] [ALU] [aqm] The Impact of Active Queue Management on DASH-based ContentDelivery
Date: Tue, 10 Jan 2017 17:37:22 +0000 [thread overview]
Message-ID: <1BFAC0A1D7955144A2444E902CB628F8D641D35C@US70TWXCHMBA12.zam.alcatel-lucent.com> (raw)
In-Reply-To: <CAA93jw7kWJhmr-Su+BptKYo7P7DUmo5vsLDswBcpZSia+KvyjA@mail.gmail.com>
It looks like tcp_slow_start_after_idle was not disabled in the experiments. If this is indeed the case, it would be interesting to see what happens when the option is disabled at the server, so that the transmission of a new chunk can start at a generally faster rate. 4K video makes this option even more relevant, especially when RTT is large.
With tcp_slow_start_after_idle disabled, the fq_nocodel scheme of Toke's study (http://dx.doi.org/10.1016/j.comnet.2015.07.014) would also be good to evaluate, especially with a total buffer size much larger than BDP: DASH does not suffer from self-inflicted delay as much as it does from packet losses, and empties its dedicated queue in between video chunks.
Andrea
-----Original Message-----
From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Dave Taht
Sent: Tuesday, January 10, 2017 11:08 AM
To: bloat <bloat@lists.bufferbloat.net>; aqm@ietf.org
Subject: [ALU] [aqm] The Impact of Active Queue Management on DASH-based ContentDelivery
This was quite good. I particularly liked the invention of the
"instability index".
Jonathan Kua, Grenville Armitage and Philip Branch, "The Impact of
Active Queue Management on DASH-based Content Delivery," in 41st
Annual IEEE Conference on Local Computer Networks (LCN), Dubai, UAE, 7
- 10 November 2016, https://doi.org/10.1109/LCN.2016.24
(more easily available via: http://sci-hub.bz/10.1109/LCN.2016.24# )
I hope a test like this gets repeated against BBR (and for that
matter, cake), and against a larger dynamic range of bandwidths (4k
video, anyone)?
_______________________________________________
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm
prev parent reply other threads:[~2017-01-10 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 16:08 [Bloat] The Impact of Active Queue Management on DASH-based Content Delivery Dave Taht
2017-01-10 17:37 ` Francini, Andrea (Nokia - US) [this message]
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=1BFAC0A1D7955144A2444E902CB628F8D641D35C@US70TWXCHMBA12.zam.alcatel-lucent.com \
--to=andrea.francini@nokia-bell-labs.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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