Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Andy Furniss <adf.lists@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] 5ms target hurting tcp throughput tweakable?
Date: Sun, 26 Feb 2017 23:21:04 +0100	[thread overview]
Message-ID: <028AA856-B11E-4025-B1BD-84BAC6768508@gmx.de> (raw)
In-Reply-To: <3c0c8aab-2a9a-82a4-0828-d58c604d35dc@gmail.com>

Looking at tc-adv, I would recommend to use “rtt 50” (maybe it is “rtt 50ms”) which allows to directly explicitly request a new “interval” (which IIRC is corresponding to the time you allow for the TCP control loop to react to cake’s ecn-marking/dropping) “target’ will be calculated as 5% of the explicit interval, in accordance with the rationale in the codel RFC.

Best Regards



> On Feb 26, 2017, at 15:34, Andy Furniss <adf.lists@gmail.com> wrote:
> 
> Jonathan Morton wrote:
>> 
>>> On 26 Feb, 2017, at 15:16, Andy Furniss <adf.lists@gmail.com> wrote:
>>> 
>>> Is there any way or plans to allow users to relax slightly the target?
>> 
>> You can do that by selecting a higher assumed RTT, for instance with the “oceanic” or “satellite” keywords.  This also increases the interval, which makes the AQM less aggressive in general.
> 
> Ok, thanks, I'll try.
> 
> I didn't know what the implications of "lying" about RTT were.
> 
> I do know that on a 60mbit ingress test I did to london = 10ms away, when I
> tried using metro = 10ms I killed single threaded throughput, so was
> wary of changing defaults after that.
> 
> 
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


  reply	other threads:[~2017-02-26 22:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 13:16 Andy Furniss
2017-02-26 13:43 ` Jonathan Morton
2017-02-26 14:34   ` Andy Furniss
2017-02-26 22:21     ` Sebastian Moeller [this message]
2017-02-27 18:02       ` Andy Furniss
2017-02-27 18:13         ` Sebastian Moeller
2017-02-27 19:26           ` Andy Furniss
2017-03-01  2:16             ` Benjamin Cronce
2017-03-01 22:48               ` Andy Furniss

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=028AA856-B11E-4025-B1BD-84BAC6768508@gmx.de \
    --to=moeller0@gmx.de \
    --cc=adf.lists@gmail.com \
    --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