From: Pete Heist <peteheist@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake flenter results round 1
Date: Mon, 27 Nov 2017 19:45:41 +0100 [thread overview]
Message-ID: <46889DF8-0D83-4729-A7D7-70CE7E599685@gmail.com> (raw)
In-Reply-To: <85E1A7B2-8AA7-418A-BE43-209A1EC8881A@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
> On Nov 27, 2017, at 12:04 PM, Pete Heist <peteheist@gmail.com> wrote:
>
> * And then above 200mbit, fq_codel performs considerably better than cake at the 32/32 flow tests. At 900mbit, UDP/ping is 1.1ms for fq_codel and 10ms for cake. TCP RTT is ~6.5ms for fq_codel and ~12ms for cake. Dave’s earlier explanation probably applies here: "Since fq_codel supports superpackets and cake peels them, we have a cpu and latency hit that originates from that. Also the code derived algorithm in cake differs quite significantly from mainline codel, and my principal gripe about it has been that it has not been extensively tested against higher delays."
>
> http://www.drhleny.cz/bufferbloat/cake/round1/32flows_eg_fq_codel_900mbit/index.html <http://www.drhleny.cz/bufferbloat/cake/round1/32flows_eg_fq_codel_900mbit/index.html>
> http://www.drhleny.cz/bufferbloat/cake/round1/32flows_eg_cakeeth_900mbit/index.html <http://www.drhleny.cz/bufferbloat/cake/round1/32flows_eg_cakeeth_900mbit/index.html>
I would not be surprised to find out that this result was also due to lack of CPU, since there’s a steady degradation in Cake’s performance above 200mbit. Next time I’ll try 8/8 flows in addition.
[-- Attachment #2: Type: text/html, Size: 1897 bytes --]
next prev parent reply other threads:[~2017-11-27 18:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 11:04 Pete Heist
2017-11-27 11:10 ` Toke Høiland-Jørgensen
2017-11-27 11:12 ` Pete Heist
2017-11-27 12:18 ` Jonathan Morton
2017-11-27 13:05 ` Pete Heist
2017-11-27 14:01 ` Jonathan Morton
2017-11-27 14:07 ` Pete Heist
2017-11-27 14:34 ` Pete Heist
2017-11-27 14:48 ` Jonathan Morton
2017-11-27 15:53 ` Pete Heist
2017-11-27 16:17 ` Georgios Amanakis
2017-11-27 17:32 ` Pete Heist
2017-11-27 17:33 ` Dave Taht
2017-11-27 17:34 ` Sebastian Moeller
2017-11-27 17:38 ` Dave Taht
2017-11-27 17:50 ` Pete Heist
2017-11-27 17:35 ` Pete Heist
2017-11-27 18:13 ` Dave Taht
2017-11-27 18:21 ` Pete Heist
2017-11-27 18:45 ` Pete Heist [this message]
2017-11-27 19:06 ` Georgios Amanakis
2017-11-27 20:37 ` Toke Høiland-Jørgensen
2017-11-27 20:50 ` Dave Taht
2017-11-27 20:53 ` Pete Heist
2017-11-27 21:08 ` Toke Høiland-Jørgensen
2017-11-27 21:17 ` Pete Heist
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=46889DF8-0D83-4729-A7D7-70CE7E599685@gmail.com \
--to=peteheist@gmail.com \
--cc=cake@lists.bufferbloat.net \
/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