Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Jeff Weeks <jweeks@sandvine.com>
Cc: "Agarwal, Anil" <Anil.Agarwal@viasat.com>,
	"Dave Täht" <dave@taht.net>, "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] [aqm] [Codel]  codel with low shape rates
Date: Tue, 19 Jan 2016 20:00:02 +0200	[thread overview]
Message-ID: <BBA0ABC1-8B00-4BF5-B1E9-937D2A840E2C@gmail.com> (raw)
In-Reply-To: <274D3A0FA900FD47AA6B56991AAA32FDC548019C@wtl-exchp-1.sandvine.com>


> On 19 Jan, 2016, at 19:32, Jeff Weeks <jweeks@sandvine.com> wrote:
> 
> Dave, What does HTB stand for?  I'm not familiar with it.

Hierarchical Token Bucket.  It’s one of the two most commonly used shapers on Linux, the other being HFSC.

> Perhaps this is an area where fq_codel would perform better?

Very likely.  My experience is that flow isolation (which is what fq_codel adds over plain codel) gives the single biggest improvement to perceived traffic quality of all the techniques I’ve seen and used.  Codel also works significantly better when it only needs to signal to one flow at a time.

If you plan to try out HTB+fq_codel or HFSC+fq_codel, then I would also suggest trying out Cake.  It’s slightly more involved to set up since it’s not yet upstream, but it’s a no-knobs-needed solution using even more sophisticated and comprehensive algorithms than fq_codel.  I’ve just finished adding “triple isolation” to it, and I plan to make it the default in the near future, unless someone turns up a major problem.

- Jonathan Morton


  parent reply	other threads:[~2016-01-19 18:02 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] [aqm] " 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       ` Jonathan Morton [this message]
2016-01-19 18:09     ` Jonathan Morton

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=BBA0ABC1-8B00-4BF5-B1E9-937D2A840E2C@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