Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>,
	Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake latency update
Date: Fri, 10 Feb 2017 13:21:49 +0100	[thread overview]
Message-ID: <531AF998-D1B2-43A6-A55B-F0471C0164E1@gmail.com> (raw)
In-Reply-To: <70520D3D-D381-44DC-A789-BB1E24FBE3F4@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 5557 bytes --]


> On Feb 10, 2017, at 12:35 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
> 
> Hi Pete,
> 
>> On Feb 10, 2017, at 12:08, Pete Heist <peteheist@gmail.com> wrote:
>> 
>> Not a problem. I’ll run a spread of Cake and fq_codel over Ethernet at various bandwidths. It will be through their Apple USB Ethernet adapters (used now for management), which are also connected through a switch, but I think that setup should be fine for this purpose. Should be done in a hour or so and we’ll see…
> 
> 	I believe the Apple USB dongles are fastEthernet only, at least the USB2 types I have available here, which for your tested bandwidth would work, but it will not allow you test at what shaper rate things go pear shaped… Also it wifi creates a bit more CPU load than wired ethernet, it _might_ make sense to concurrently excercise the WIFI cards just to re-create the SIRQ load (but probably not as the first experiment ;) ).
> 
> Best Regards
> 	Sebastian 

Hi Sebastian, yes, they’re only 100 Mbit, but that’s enough to cover the rates where I was seeing the problem with Wi-Fi. Also in my test setup there are four nodes connected as described under Configuration #1:

http://www.drhleny.cz/bufferbloat/wifi_bufferbloat.html <http://www.drhleny.cz/bufferbloat/wifi_bufferbloat.html>

I’m running Cake on ‘mini’ and ‘mbp’, and the Wi-Fi radios are only on ‘om1’ and ‘om2’, so the CPU load shouldn’t be different for mini and mbp when connected directly via Ethernet, instead of via Ethernet and a Wi-Fi link, I suppose.

I think we just wanted to see if the throughput shifting would reproduce over Ethernet at the same rates, but so far it didn’t for me, although there are other anomalies that don’t look like the throughput shifts I sent before (there’s a throughput anomaly for Cake 20Mbit and latency anomalies for fq_codel 60Mbit and 90Mbit):

http://www.drhleny.cz/bufferbloat/cake_hd-eth_10mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_10mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_20mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_20mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_30mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_30mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_40mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_40mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_50mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_50mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_60mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_60mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_70mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_70mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_75mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_75mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_80mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_80mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_85mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_85mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_90mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_90mbit/index.html>

http://www.drhleny.cz/bufferbloat/cake_hd-eth_100mbit/index.html <http://www.drhleny.cz/bufferbloat/cake_hd-eth_100mbit/index.html>

fq_codel:

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_10mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_10mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_20mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_20mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_30mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_30mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_40mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_40mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_50mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_50mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_60mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_60mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_70mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_70mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_75mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_75mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_80mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_80mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_85mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_85mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_90mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_90mbit/index.html>

http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_100mbit/index.html <http://www.drhleny.cz/bufferbloat/fq_codel_hd-eth_100mbit/index.html>

So that suggests that the throughput shifting problem may also be somehow related to Wi-Fi. I’m still going to be testing Chaos Calmer, as well as two Ubiquiti NanoStation M5’s, though this will take some more time. We might learn some more from this, or if you can reproduce it with ath9k hardware that would be good too...

Thanks,
Pete


[-- Attachment #2: Type: text/html, Size: 12812 bytes --]

  reply	other threads:[~2017-02-10 12:21 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
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 [this message]
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=531AF998-D1B2-43A6-A55B-F0471C0164E1@gmail.com \
    --to=peteheist@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