Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Loganaden Velvindron <loganaden@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Running Cake at long RTTs
Date: Tue, 27 Oct 2015 15:16:54 +0000	[thread overview]
Message-ID: <CAOp4FwQ=CnH62PzY9-TfRgH6iiGEeHKG6ijocXeXyu5K+8Sozg@mail.gmail.com> (raw)
In-Reply-To: <87a8r4mji9.fsf@toke.dk>

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

On Tue, Oct 27, 2015 at 3:14 PM, Toke Høiland-Jørgensen <toke@toke.dk>
wrote:

> So Dave and I did a bit of testing of Cake at a 1-second base RTT. That
> showed that, compared with a straight FIFO queue (with a sufficiently
> large buffer), throughput was suffering quite a bit under Cake,
> especially at large bandwidths. We did two changes to fix this:
>
> - Turn the hard packet queue size into a lower bound rather than an
>   upper bound.
>
> - Scale the target to be 1/16th of the interval.
>
> The first change allows Cake to actually reach the target throughput,
> but it still takes a long while to get there. With the second change, we
> actually get the desired behaviour. The attached plot shows the
> difference, with the solid line being before the change and the dashed
> line being after the change.
>
> Patch attached.
>
> Fantastic !

I'm going to test it and report back. I'm interested in how this will
perform for 350ms RTT.



> -Toke
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
>

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

  reply	other threads:[~2015-10-27 15:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 15:14 Toke Høiland-Jørgensen
2015-10-27 15:16 ` Loganaden Velvindron [this message]
     [not found] ` <6499FF74-D13B-4B2E-90E3-D1FDD3FD1468@gmx.de>
2015-10-27 16:50   ` Toke Høiland-Jørgensen
2015-10-27 17:14     ` Sebastian Moeller
2015-10-27 19:04 ` Jonathan Morton
2015-10-27 23:57   ` Toke Høiland-Jørgensen
2015-10-28  9:36     ` Sebastian Moeller
2015-10-28 15:28 ` Sebastian Moeller
2015-10-28 15:36   ` Toke Høiland-Jørgensen
2015-10-28 15:50     ` Sebastian Moeller
2015-10-28 16:34       ` Toke Høiland-Jørgensen
2015-10-28 17:44         ` Sebastian Moeller
2015-10-29 17:36 ` Kevin Darbyshire-Bryant
2015-10-30 20:30   ` Kevin Darbyshire-Bryant
2015-10-30 21:34   ` Dave Taht

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='CAOp4FwQ=CnH62PzY9-TfRgH6iiGEeHKG6ijocXeXyu5K+8Sozg@mail.gmail.com' \
    --to=loganaden@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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