From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake at longer rtts
Date: Wed, 18 Jan 2017 07:51:46 +0200 [thread overview]
Message-ID: <1794DF2C-108F-488D-AE25-48B1D87F36E5@gmail.com> (raw)
In-Reply-To: <CAA93jw5xRzrOG1F56OC+sxj98AbBQ3ZEc0KZFyatwXbq-9=4KA@mail.gmail.com>
> On 18 Jan, 2017, at 05:35, Dave Taht <dave.taht@gmail.com> wrote:
>
> It has been quite some time since I looked at cake at longer RTTs.
>
> Here's a single flow test comparing it to sonic fiber default fifo
> (50ms delay in the ONT), to fq_codel, to cake at 110mbit.
>
> http://www.taht.net/~d/sonic_cake_vs_fq_codel_vs_fifo_70ms.png
Seems to be more aggressive than fq_codel on the slow-start response, but very similar thereafter. I think that’s consistent with what I believe I’ve implemented, and with some tests I’ve been running over here.
In my experience, Westwood+ performs better than CUBIC with Codel, because it estimates the true BDP better and hops directly to it when the signal arrives. Probably BBR has similar properties, but with different semantics.
I sometimes use longer assumed-RTTs, ie. “oceanic” or “satellite”, in order to get a little more throughput. However, this significantly reduces the latency control in ingress mode, because every slow-start is then uncontrolled for a full second.
- Jonathan Morton
next prev parent reply other threads:[~2017-01-18 5:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 3:35 Dave Taht
2017-01-18 5:51 ` Jonathan Morton [this message]
2017-01-18 5:59 ` Jonathan Morton
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=1794DF2C-108F-488D-AE25-48B1D87F36E5@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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