From: Dave Taht <dave@taht.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Steinar H. Gunderson" <sgunderson@bigfoot.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dash traffic "chunklets" verses pie and fq_codel
Date: Fri, 08 Sep 2017 11:14:45 -0700 [thread overview]
Message-ID: <87ingtrrai.fsf@nemesis.taht.net> (raw)
In-Reply-To: <CAJq5cE2amqrShQk0zO3VSW_2FAzK2rZt83qafWScV+q8xoZRtQ@mail.gmail.com> (Jonathan Morton's message of "Fri, 8 Sep 2017 14:50:26 +0300")
Jonathan Morton <chromatix99@gmail.com> writes:
> While interesting from a scientific point of view, I do think they're trying to
> solve the wrong problem here.
I am always interested in someone repeating an experiment with a few
more variables altered. In this case, pacing and BBR would be rather
interesting to see.
>
> As stated in the paper, the big problem with DASH is the tendency of TCPs to
> revert to slow start (ie. beginning from a small cwnd) after a gap in
> availability of data to transmit. If that occurs after as short an interval as 2
> seconds (the DASH chunk length), I consider that to be a flaw in those TCP
> implementations.
We also have the decay factors present in the available AQMs.
> Theoretically, 2 seconds is as long as DASH should wait while playing video
> continuously, in the steady state condition where the link capacity is known and
> the buffer is full. I can see little reason for it to wait longer; I would
> consider that an implementation flaw in the DASH client.
>
> Also, given a nearly full buffer, I would expect DASH to resist reducing the
> video quality due to a possibly transient reduction in measured link capacity.
> If the reduction persists long enough to substantially empty the buffer (say to
> 50%), then it would be reasonable to step down in quality to match the new
> measurement. Again, this is a quality of implementation problem in the client.
>
> The other problem their solution addresses, but is not stated as the primary
> goal, is to reduce DASH susceptibility to competition versus multiple flow
> applications such as Steam downloads. But that is not a problem specific to flow
> isolating AQM systems (if anything, it's worse with plain FIFO). They do note
> that fq_codel greatly improves the situation versus reverse bulk traffic, just
> as it should, but they don't seem to highlight that this benefit is reduced with
> "chunklets" in use, according to the measurements presented.
My overall joy is generally that "things are better" with fq_codel based queuing
solutions than anything else we've yet devised, for yet another form of
traffic.
Really the only thing left that I worry about (technically) is
videoconferencing. It's crossing the chasm to the places where these
technologies are most needed - where we have devices with first
world fifo over-buffering being deployed into third world bandwidths,
and still no headends for any last mile tech (dsl, cable, etc) actually
implementing stuff like this. There's a lot of the world left to cover
with better Internet.
https://trends.google.com/trends/explore?q=bufferbloat
>
> - Jonathan Morton
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2017-09-08 18:14 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 [this message]
2017-09-08 17:51 ` Dave Taht
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=87ingtrrai.fsf@nemesis.taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--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