From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cake@lists.bufferbloat.net,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Cake] [Codel] hard limit codel
Date: Thu, 16 Apr 2015 13:50:53 +0200 [thread overview]
Message-ID: <87twwg5m1u.fsf@toke.dk> (raw)
In-Reply-To: <AE067EE3-0B24-4DB9-82E8-074169BDD976@gmail.com> (Rich Brown's message of "Thu, 16 Apr 2015 00:25:01 -0400")
Rich Brown <richb.hanover@gmail.com> writes:
> Please don't fisk this. The paper is *way* too long to be worth a
> sentence-by-sentence refutation of every inaccuracy or outright
> wrong-headed understanding of Codel... :-)
I think this paragraph pretty much sums it up:
"Actually, the throughput of hard limit CoDel is signifi- cantly lower
than the original CoDel only when the RTT is large (500ms), the
bandwidth is high (64 Mbps) with only one TCP flow, in which case the
throughput is only 4.1 Mbps, 63% lower than that of the original CoDel.
Though it may seem to be a significant loss, we argue that it is
acceptable because even in the worst case, a bit rate of 4 Mbps is
sufficient to support today’s 720p videos. The link utilization is much
higher when either of the three conditions changes."
Surely, 4Mbps is enough for everybody?
I'll add, though, that I have seen the sentiment expressed here ("we
need to limit the max delay of CoDel") in other contexts. And, well,
delay spikes *is* a problem!
-Toke
next prev parent reply other threads:[~2015-04-16 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 3:23 [Cake] " Dave Taht
2015-04-16 4:25 ` [Cake] [Codel] " Rich Brown
2015-04-16 11:50 ` Toke Høiland-Jørgensen [this message]
2015-04-16 12:00 ` Jonathan Morton
2015-04-16 12:10 ` Andrew McGregor
2015-04-16 14:47 ` Kathleen Nichols
2015-04-16 15:02 ` Toke Høiland-Jørgensen
2015-04-16 16:04 ` Kathleen Nichols
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twwg5m1u.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=richb.hanover@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