From: Pete Heist <peteheist@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake latency update
Date: Fri, 10 Feb 2017 09:04:03 +0100 [thread overview]
Message-ID: <830143EE-20F2-42A5-A4FC-ECE7DF50C632@gmail.com> (raw)
In-Reply-To: <3D9E1A43-0182-4A1F-8262-6F587A79254E@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2130 bytes --]
> On Feb 9, 2017, at 9:52 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 9 Feb, 2017, at 18:36, Pete Heist <peteheist@gmail.com> wrote:
>>
>> I’m seeing good latency results for Cake at lower MCS levels (graphs below), in case that wasn’t already known.
>
> Yes - despite its complexity, Cake has always performed well on latency in comparison to other qdiscs.
>
> I gather this time you’re comparing it against the mac80211 fq_codel, rather than a conventional qdisc stack?
Yes, this is on stock LEDE, and I hope to complete results on Chaos Calmer.
I haven’t always seen Cake’s latency numbers lower compared to fq_codel. If I take these two:
http://www.drhleny.cz/bufferbloat/fq_codel_fd-wifi-both_40mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_fd-wifi-both_40mbit/index.html>
http://www.drhleny.cz/bufferbloat/cake_fd-wifi-both_40mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_fd-wifi-both_40mbit/index.html>
FQ-CoDel did better in this case, but it was running on the AP (OM2P-HS, 520 MHz MIPS 74Kc). When run on higher powered Intel routers it basically tied fq_codel:
http://www.drhleny.cz/bufferbloat/cake_fd-eth-ap_100ms_40mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_fd-eth-ap_100ms_40mbit/index.html>
http://www.drhleny.cz/bufferbloat/fq_codel_fd-eth-ap_target_5ms_interval_100ms_40mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_fd-eth-ap_target_5ms_interval_100ms_40mbit/index.html>
but then as you lower the bitrate, Cake’s performance on the rrul test seems to get better relative to fq_codel:
http://www.drhleny.cz/bufferbloat/mcstmp/mcs_latency.png <http://www.drhleny.cz/bufferbloat/mcstmp/mcs_latency.png>
I look forward to the throughput shifts being solved, where I see results like this:
http://www.drhleny.cz/bufferbloat/cake_hd-eth-ap_100ms_80mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth-ap_100ms_80mbit/index.html>
This is the only thing so far that would keep me from recommending it for my ISP to test. Otherwise the results from Cake are promising… :)
Pete
[-- Attachment #2: Type: text/html, Size: 3486 bytes --]
next prev parent reply other threads:[~2017-02-10 8:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 16:36 Pete Heist
2017-02-09 20:52 ` Jonathan Morton
2017-02-10 8:04 ` Pete Heist [this message]
2017-02-10 8:49 ` Jonathan Morton
2017-02-10 9:21 ` Pete Heist
2017-02-10 9:29 ` Jonathan Morton
2017-02-10 10:05 ` Pete Heist
2017-02-10 10:31 ` Jonathan Morton
2017-02-10 11:08 ` Pete Heist
2017-02-10 11:35 ` Sebastian Moeller
2017-02-10 12:21 ` Pete Heist
2017-02-12 12:43 ` Pete Heist
2017-02-12 13:08 ` Dave Taht
2017-02-12 14:12 ` Pete Heist
2017-02-12 16:37 ` Pete Heist
2017-02-12 16:41 ` Jonathan Morton
2017-02-12 17:15 ` Pete Heist
2017-02-14 10:02 ` 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=830143EE-20F2-42A5-A4FC-ECE7DF50C632@gmail.com \
--to=peteheist@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