Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Luis E. Garcia" <luis@bitamins.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] A quick question about FQ_CoDel vs Cake
Date: Fri, 07 Apr 2017 02:51:59 +0000	[thread overview]
Message-ID: <CALnBQ5n46e7hWrNhD2_LBN3B6Ru1KsiV37FQuUAsmPC3+kDGZg@mail.gmail.com> (raw)
In-Reply-To: <3FFFF4B7-6DF7-4F7B-8F2D-5E22E27769FB@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]

Thanks Jonathan,
With this explanation it makes sense.

Regards,
Luis

On Thu, Apr 6, 2017 at 11:06 AM Jonathan Morton <chromatix99@gmail.com>
wrote:

>
> > On 6 Apr, 2017, at 16:51, Luis E. Garcia <luis@bitamins.net> wrote:
> >
> > I've been doing some testing of Cake on LEDE (WD MyNet 750) and on
> EdgeOS (Ubiquity ERPoe). One big question that I have is why does Cake have
> a higher/better average throughput than FQ_CoDel? The graph seems a bit
> smoother through the speed test.
> >
> > The test are against a 10down/2up Mbps connection from a local provider.
>
> The main difference that’s probably responsible for this is Cake’s
> integrated deficit-mode shaper, which is more accurate on short timescales
> than the more typical token-bucket shaper that fq_codel is used with.
>
> There’s also some difference in the Codel implementation which might or
> might not be relevant, specifically in the calculation of “count” after a
> relatively brief exit from dropping state.
>
>  - Jonathan Morton
>
>

[-- Attachment #2: Type: text/html, Size: 1661 bytes --]

      reply	other threads:[~2017-04-07  2:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 13:51 Luis E. Garcia
2017-04-06 17:06 ` Jonathan Morton
2017-04-07  2:51   ` Luis E. Garcia [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=CALnBQ5n46e7hWrNhD2_LBN3B6Ru1KsiV37FQuUAsmPC3+kDGZg@mail.gmail.com \
    --to=luis@bitamins.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@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