General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: John Klimek <jklimek@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Difference between codel and fq_codel?
Date: Wed, 03 Feb 2016 21:33:27 +0100	[thread overview]
Message-ID: <878u31r0tk.fsf@alrua-karlstad.karlstad.toke.dk> (raw)
In-Reply-To: <E0206F34-5540-4D33-A4AB-4B3A765D0B4D@gmail.com> (John Klimek's message of "Wed, 3 Feb 2016 14:22:53 -0500")

John Klimek <jklimek@gmail.com> writes:

> 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?

Yes, and quite possibly. :)

Basically, Codel drops packets to try to keep queues small. This works
reasonably well. However, what FQ-CoDel adds is flow isolation and
priority for sparse flows, which is what in most cases gets rid of
almost all of the added latency under load.

For a (much) longer version of the above, see this:
http://www.sciencedirect.com/science/article/pii/S1389128615002479 -- In
particular, figure 2 shows the performance of a bunch of different
algorithms, including CoDel and FQ-CoDel :)

-Toke

      parent reply	other threads:[~2016-02-03 20:33 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
2016-04-08 19:37   ` Jim Gettys
2016-02-03 20:33 ` Toke Høiland-Jørgensen [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/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=878u31r0tk.fsf@alrua-karlstad.karlstad.toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jklimek@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