Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Jonathan Morton <chromatix99@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] 5ms target hurting tcp throughput tweakable?
Date: Mon, 27 Feb 2017 18:02:04 +0000	[thread overview]
Message-ID: <9353cc42-220b-af1b-3105-19be52ed0627@gmail.com> (raw)
In-Reply-To: <028AA856-B11E-4025-B1BD-84BAC6768508@gmx.de>

Sebastian Moeller wrote:
> 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.

50 is certainly better than 10, but still seems to hurt single a bit
even on a close server.

On more distant servers maybe even more - I am getting results that are
too variable to tell properly at the current time (of day).

http://www.thinkbroadband.com/speedtest/results.html?id=1488216166262542155

Almost OK, but with 100ms this test usually shows x1 and x6 the same.

http://www.thinkbroadband.com/speedtest/results.html?id=1488218291872647755

Of course as we all know ingress shaping is a different beast anyway and
would deserve its own thread.

  reply	other threads:[~2017-02-27 18:02 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
2017-02-27 18:02       ` Andy Furniss [this message]
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=9353cc42-220b-af1b-3105-19be52ed0627@gmail.com \
    --to=adf.lists@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --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