From: Luca De Cicco <ldecicco@gmail.com>
To: "Dave Täht" <dave@taht.net>, aqm@ietf.org, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [aqm] HAS traffic behaviors
Date: Thu, 03 Mar 2016 18:49:53 -0000 [thread overview]
Message-ID: <CACHLvedOB3OBB4s-FO3MQ3QCo1=W9YDQ7XsDbZp2=atu-8w1Sg@mail.gmail.com> (raw)
In-Reply-To: <56D861AC.4040506@taht.net>
[-- Attachment #1: Type: text/plain, Size: 3822 bytes --]
Dear Dave,
thanks a bunch for your feedback. My reply is inline.
On Thu, Mar 3, 2016 at 5:05 PM Dave Täht <dave@taht.net> wrote:
> On 3/3/16 4:31 AM, Luca De Cicco wrote:
> > Dear Ingemar and all,
> >
> > I hope not to hijack the topic,
>
> No worries, but I changed the subject line to suit. I strongly support
> those writing papers to submit them for discussion to the lists... I
> read google scholar regularly but missed these.
>
Great. Thanks for taking time to browse the papers :)
> >but I would like to add some bits to the
> > interesting HAS/DASH
> > discussion you bootstrapped.
> > Regarding the performance of HAS/DASH adaptive streaming control
> > algorithm, the reason for the
> > poor performance of rate-based algorithms is due to the ON/OFF behaviour
> > of the clients (i.e. video clients
> > insert idle periods to control the buffer and concurrent TCP flows can
> > take advantage of this).
> > This phenomenon was first uncovered in the IMC 2012 paper that Te-Yuan
> > et al. named "the downward
> > spiral effect" and is also experimentally shown in the following paper
> > in the case of several "rate based" algorithms
> > (sorry for the advertisement ;)) where we proposed a buffer-based
> > adaptive streaming control algorithm:
> >
> > http://c3lab.poliba.it/images/a/a1/Elastic-pv2013.pdf
> > L. De Cicco, V. Caldaralo, V. Palmisano, and S. Mascolo
> > ELASTIC: a Client-side Controller for Dynamic Adaptive Streaming over
> > HTTP (DASH)
> > Proc. of Packet Video Workshop 2013, San Jose, CA, USA, December 2013
>
> This experiment can be easily repeated with various AQM,AQM/fq
> technologies in the link.
>
> The size of the drop tail queue is not documented...
>
>
IIRC the DT queue size was equal to the BDP. We have also run experiments
with tc/netem but we didn't study the impact of AQMs on performance.
> Is this the netshaper codebase? http://netshaper.sourceforge.net/ ?
>
> "NetShaper that performs bandwidth shaping and allows
> propagation delays to be set. This tool uses the nfqueue
> library provided by Netfilter1
> in order to capture and
> redirect the packets arriving at the client host to a user space
> drop-tail queue, where traffic shaping and measurement are
> performed."
>
> This is in a place where we would just plug the various algorithms into
> the sqm-scripts and not do it in userspace.
>
> The emulated base RTT is not documented. Arguably HAS traffic would
> often have a lower base RTT than a random tcp link.
>
>
IIRC the baseRTT was set equal to 50ms.
> The dynamic range of the selected rates seems low.
>
What do you mean by selected rates?
> I am always harping on the need to test against an upload flow, and to
> emulate asymmetric network links common in the home, in general.
>
> > A more theoretical explanation of rate-based and buffer-based approaches
> > can be found here
> > where some properties of hysteresis buffer-based controllers are shown:
> >
> > http://c3lab.poliba.it/images/b/b1/Acc2015.pdf
>
> Read this also. I guess a key thing I keep wanting to see is the effect
> of a web traffic burst - and the reaction time changes with an upload
> going on at the same time.
This can be easily set up. We have released a tool which is able to
generate a relatively high number of HAS flows using a single machine
(decoding/rendering of the video can be turned off but the dynamics of the
control algorithm is not impacted). The tool is also useful to
implement/compare different adaptive streaming control algos.
Please look at:
https://github.com/ldecicco/tapas
and the companion paper:
http://c3lab.poliba.it/images/f/f3/Tapas-videonext.pdf
(And now I swear I'll stop with the advertisement!)
Cheers,
Luca
[-- Attachment #2: Type: text/html, Size: 5436 bytes --]
prev parent reply other threads:[~2016-03-03 18:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56BB8F05.2030006@mti-systems.com>
[not found] ` <BF6B00CC65FD2D45A326E74492B2C19FB763038A@FR711WXCHMBA05.zeu.alcatel-lucent.com>
2016-02-27 19:04 ` [Bloat] review: Deployment of RITE mechanisms, in use-case trial testbeds report part 1 Dave Täht
2016-02-28 13:33 ` Alan Jenkins
2016-02-28 13:39 ` Toke Høiland-Jørgensen
2016-02-28 14:26 ` Alan Jenkins
2016-02-28 20:20 ` Juliusz Chroboczek
2016-02-28 21:27 ` Toke Høiland-Jørgensen
2016-02-28 21:24 ` Toke Høiland-Jørgensen
2016-02-29 17:55 ` Dave Taht
2016-03-02 11:26 ` [Bloat] [aqm] " De Schepper, Koen (Nokia - BE)
2016-03-02 18:09 ` [Bloat] " Fred Baker (fred)
2016-03-02 20:53 ` Alan Jenkins
2016-03-02 21:47 ` Fred Baker (fred)
2016-03-03 12:13 ` [Bloat] [aqm] " Ingemar Johansson S
2016-03-03 12:31 ` Luca De Cicco
2016-03-03 16:09 ` [Bloat] HAS traffic behaviors Dave Täht
2016-03-03 18:49 ` Luca De Cicco [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='CACHLvedOB3OBB4s-FO3MQ3QCo1=W9YDQ7XsDbZp2=atu-8w1Sg@mail.gmail.com' \
--to=ldecicco@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave@taht.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