General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Rick Jones <rick.jones2@hpe.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Difference between codel and fq_codel?
Date: Fri, 8 Apr 2016 22:36:10 +0300	[thread overview]
Message-ID: <D7B23205-6EFD-4D3B-A3EE-AE483559C133@gmail.com> (raw)
In-Reply-To: <56B25E76.3080506@hpe.com>


> On 3 Feb, 2016, at 22:09, Rick Jones <rick.jones2@hpe.com> wrote:
> 
> On 02/03/2016 11:22 AM, John Klimek wrote:
>> I'm currently using pfaense which only supports codel and not
>> fq_codel. Is there a big difference between them?  Is it worth
>> looking into using a different router?
> 
> My simplistic understanding is fq_codel creates several/many different queues, spreading flows across those queues and applying codel on each queue.

There *is* a big difference between fq_codel and plain codel.  Simply put, the “fq” part of fq_codel is capable of mitigating inter-flow induced latency much more reliably than plain codel can.  Codel in itself manages only intra-flow induced latency.

Fq_codel maintains a separate codel instance per queue, so it also does a better job of applying the correct amount of congestion feedback to each flow, rather than a blanket amount over all traffic using the link.

The difference is particularly marked when you are dealing with congestion-unresponsive traffic (which codel is inherently poor at managing), but is measurable and even noticeable even with standard TCP flows.

 - Jonathan Morton


  reply	other threads:[~2016-04-08 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 19:22 John Klimek
2016-02-03 20:09 ` Rick Jones
2016-04-08 19:36   ` Jonathan Morton [this message]
2016-04-08 19:37   ` Jim Gettys
2016-02-03 20:33 ` Toke Høiland-Jørgensen

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=D7B23205-6EFD-4D3B-A3EE-AE483559C133@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=rick.jones2@hpe.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