Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: George Amanakis <g_amanakis@yahoo.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Cobalt testing
Date: Mon, 25 Sep 2017 20:15:47 -0400	[thread overview]
Message-ID: <1989ae75-d6a0-9b0c-5540-d69acf62bcc0@yahoo.com> (raw)

I am currently testing the cobalt branch with limited rates. The line is 
a residential cable connection (Comcast) advertised as 10Mbps (actual 
speeds are ~12500kbps ingress and ~2600kbps egress). IMO the limited 
rate is more stable after the last commits. I used the apu2.sh and 
dancer.sh scripts (from Dave, http://blog.cerowrt.org/flent/fq_host2/) 
on two different machines simultaneously. BTW, I think dancer.sh has a 
"bug", the last 2 tests should begin with "flent -6" since we want to 
test IPv6.

Config:
qdisc cake 8002: dev ens3 root refcnt 9 bandwidth 2500Kbit diffserv3 
dual-srchost nat wash rtt 100.0ms noatm overhead 18 via-ethernet mpu 64
qdisc cake 8001: dev ens4 root refcnt 9 bandwidth 12200Kbit diffserv3 
dual-dsthost wash ingress rtt 100.0ms noatm overhead 18 via-ethernet mpu 64

Due to the long nature of the results, they are to be found at 
https://pastebin.com/zRvUeCDd.

The only comment I have is that while ingress bandwidth is distributed 
consistently equally between the two hosts (eg 5.81Mbits/s for each one 
in IPv4), egress bandwidth could have been distributed better (eg 
1.06Mbits/s for apu2 vs 1.44Mbit/s for dancer).

George

.

                 reply	other threads:[~2017-09-26  0:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1989ae75-d6a0-9b0c-5540-d69acf62bcc0@yahoo.com \
    --to=g_amanakis@yahoo.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