From: Dave Taht <dave.taht@gmail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dash traffic "chunklets" verses pie and fq_codel
Date: Fri, 8 Sep 2017 10:51:37 -0700 [thread overview]
Message-ID: <CAA93jw4EnKjYKnE72y7OO92UPbB9OtZxnzuytwfSRCpEe6UvFQ@mail.gmail.com> (raw)
In-Reply-To: <20170908073215.dba5utrwuwvruw55@sesse.net>
On Fri, Sep 8, 2017 at 12:32 AM, Steinar H. Gunderson
<sgunderson@bigfoot.com> wrote:
> On Thu, Sep 07, 2017 at 04:52:54PM -0700, Dave Taht wrote:
>> good read:
>>
>> http://caia.swin.edu.au/cv/jkua/preprint/jkua-icccn2017-chunklets-preprint-10may17.pdf
>
> Aaaaa!
>
> “For example, FQ-CoDel isolates individual traffic flows into
> sub-queues then serves each sub-queue with a Deficit Round
> Robin (DRR) scheduler. The result is relatively even capacity
> sharing, which may actually be detrimental to a DASH flow
> (often a single, persistent TCP connection) that is competing
> with multiple other concurrent TCP flows.”
>
> Isn't this just an AQM sabotage scheme?
Well, first, a paper showing vastly better behavior for dash traffic
for fq_codel over pie and tail drop was a reason to celebrate.
Secondly, dash is kind of special in that you *are* constantly probing
for more bandwidth for a replacement stream, and that does interact
with fq in some difficult ways.
I wouldn't go as far as calling using two flows to do a probe like
this "sabotage", but a practical means of finding the right queue and
getting a bit more bandwidth overall. The multipath mosh work (sadly
still not mainlined when last I looked) was resistant to hash
collisions.
It is unclear from the paper to what extent the aqm kicks in - I would
have liked some packet drop figures and their onset.
I keep hoping to see some resumption of bittorrent experiments...
Lastly, I liked the idea of a (in)stability index.
> /* Steinar */
> --
> Homepage: https://www.sesse.net/
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
prev parent reply other threads:[~2017-09-08 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 23:52 Dave Taht
2017-09-08 7:32 ` Steinar H. Gunderson
2017-09-08 11:50 ` Jonathan Morton
2017-09-08 18:14 ` Dave Taht
2017-09-08 17:51 ` Dave Taht [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=CAA93jw4EnKjYKnE72y7OO92UPbB9OtZxnzuytwfSRCpEe6UvFQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=sgunderson@bigfoot.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