Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: "Agarwal, Anil" <Anil.Agarwal@viasat.com>
Cc: "Dave Täht" <dave@taht.net>, "Jeff Weeks" <jweeks@sandvine.com>,
	"aqm@ietf.org" <aqm@ietf.org>,
	"cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>,
	"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Cake] [Codel] [aqm] codel with low shape rates
Date: Tue, 19 Jan 2016 20:09:35 +0200	[thread overview]
Message-ID: <BDC7DCA7-3979-462E-998E-CB593CD91BD9@gmail.com> (raw)
In-Reply-To: <7A2801D5E40DD64A85E38DF22117852C881A1224@wdc1exchmbxp05.hq.corp.viasat.com>


> On 19 Jan, 2016, at 15:43, Agarwal, Anil <Anil.Agarwal@viasat.com> wrote:
> 
> (I would like very much to have an aqm that was knobless at these speeds. Most of the work on trying to improve matters at these rates is in the multitude of "cake" variants)

Codel is pretty close to being self-tuning in terms of link capacity, as long as it’s on the bottleneck and only needs to deal with one flow per instance.  The main trouble is when the inherent serialisation delay becomes comparable to the time constants assumed for the total estimated RTT.  On very slow links, the a-priori RTT estimate needs to be increased to account for that.

Cake has an advantage here in knowing the link capacity, via its built-in shaper.  This is how it knows what fine-tuning to apply.  It’s hard for a “pure” AQM qdisc to gather that information automatically.

With that self-tuning, Cake works usably well down to 64Kbps.  At that level, typical modern TCPs (especially CUBIC) saturate the link continuously from the outset, so Codel ends up constantly signalling them to slow down.  With ECN on, this is harmless.

 - Jonathan Morton


      parent reply	other threads:[~2016-01-19 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <274D3A0FA900FD47AA6B56991AAA32FDC547FC0F@wtl-exchp-1.sandvine.com>
2016-01-18 22:57 ` [Cake] " Dave Täht
2016-01-19 13:43   ` [Cake] [Codel] " Agarwal, Anil
     [not found]     ` <274D3A0FA900FD47AA6B56991AAA32FDC548019C@wtl-exchp-1.sandvine.com>
2016-01-19 18:00       ` [Cake] [aqm] [Codel] " Jonathan Morton
2016-01-19 18:09     ` Jonathan Morton [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/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=BDC7DCA7-3979-462E-998E-CB593CD91BD9@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=Anil.Agarwal@viasat.com \
    --cc=aqm@ietf.org \
    --cc=cake@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave@taht.net \
    --cc=jweeks@sandvine.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