Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
	moeller0 <moeller0@gmx.de>,
	cake@lists.bufferbloat.net
Subject: Re: [Cake] second system syndrome
Date: Wed, 23 Dec 2015 15:06:28 +0200	[thread overview]
Message-ID: <021986E5-5915-4D60-A391-6C6151AA6EBC@gmail.com> (raw)
In-Reply-To: <CAA93jw5Qe4LX1u1hJ5yWWcWv-xFcamt+m54RRWSC=XkQU7J9nA@mail.gmail.com>


> On 23 Dec, 2015, at 14:41, Dave Taht <dave.taht@gmail.com> wrote:
> 
> Are you actually testing your codel changes at longer RTTs?

The latest set has, so far, only been tested on an ordinary Internet link.  It produced an immediately noticeable improvement on ingress there, implying that it’s controlling the upstream queue better.

I’m reasonably confident, however, that it’ll stand up to more varied tests as well.  Fundamentally, it returns to the standard Codel trigger mechanism under most circumstances, since that’s been shown to work well.

It also adds a new wrinkle that only appears when the queue is growing very quickly, to trigger the signalling early when it’s abundantly clear that it *will* inevitably trigger later.  I think this will particularly help cope with TCP slow-start or, on a long-RTT path, with RTT-independent TCPs like CUBIC.

Feel free to run your own tests.  I need to sleep.

 - Jonathan Morton

  reply	other threads:[~2015-12-23 13:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 14:53 Dave Taht
2015-12-06 16:08 ` Sebastian Moeller
2015-12-07 12:24   ` Kevin Darbyshire-Bryant
2015-12-20 12:47     ` Dave Taht
2015-12-20 12:52       ` Dave Taht
2015-12-21  9:02         ` moeller0
2015-12-21 10:40           ` Dave Taht
2015-12-21 11:10             ` moeller0
2015-12-21 12:00               ` Dave Taht
2015-12-21 13:05                 ` moeller0
2015-12-21 15:36                   ` Jonathan Morton
2015-12-21 18:19                     ` moeller0
2015-12-21 20:36                       ` Jonathan Morton
2015-12-21 21:19                         ` moeller0
     [not found]                         ` <8737uukf7z.fsf@toke.dk>
2015-12-22 15:34                           ` Jonathan Morton
2015-12-22 22:30                     ` Kevin Darbyshire-Bryant
2015-12-23 11:43                       ` Dave Taht
2015-12-23 12:14                         ` Kevin Darbyshire-Bryant
2015-12-23 12:27                         ` Jonathan Morton
2015-12-23 12:41                           ` Dave Taht
2015-12-23 13:06                             ` Jonathan Morton [this message]
2015-12-23 14:58                               ` Dave Taht
2015-12-20 13:51       ` moeller0
2015-12-06 18:21 ` Kevin Darbyshire-Bryant

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=021986E5-5915-4D60-A391-6C6151AA6EBC@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=kevin@darbyshire-bryant.me.uk \
    --cc=moeller0@gmx.de \
    /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