Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Georgios Amanakis <g_amanakis@yahoo.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] WAN ingress rate with concurrent downloads
Date: Thu, 27 Oct 2016 21:34:14 -0400	[thread overview]
Message-ID: <1477618454.22786.3.camel@yahoo.com> (raw)
In-Reply-To: <0FA74BC3-33E0-4CF8-B134-B688EA0A4DBB@yahoo.com>

Hi Sebastian,

the ISP is Comcast in MD, USA, residential connection. It is a cable
connection (i.e. the WAN port on the modem is a coaxial one) and not a
DSL one. Maximum ingress rate is ~450kbytes/s which is what the modem
syncs at. By using "test_WAN_dual-isolate__piece_of_cake.qos", "tc -d
qdisc show" reports (enp0s13 is WAN, enp0s14 is LAN):
-------8<--------
qdisc noqueue 0: dev lo root refcnt 2 
qdisc fq_codel 0: dev enp0s14 root refcnt 2 limit 10240p flows 1024 		
quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc cake 8002: dev enp0s13 root refcnt 2 bandwidth 900Kbit besteffort
		dual-srchost nat rtt 100.0ms raw 
qdisc ingress ffff: dev enp0s13 parent ffff:fff1 ---------------- 
qdisc fq_codel 0: dev ifb0 root refcnt 2 limit 10240p flows 1024 		
quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc cake 8003: dev ifb4enp0s13 root refcnt 2 bandwidth 3300Kbit 		
besteffort dual-dsthost nat rtt 100.0ms raw 
-------8<--------

If one of the hosts on LAN is running bittorrent, bmon on the gateway
reports:
		RX bps 		RXpps	TX bps		TXpps
enp0s14		23.55KiB	303	402.87KiB	322
enp0s13		457.26KiB	369	25.04KiB	307


Setting the ingress rate at 1900kbps (instead of 3300kbps as above),
"tc -d qdisc show" reports:
-------8<--------
qdisc noqueue 0: dev lo root refcnt 2 
qdisc fq_codel 0: dev enp0s14 root refcnt 2 limit 10240p flows 1024 		
quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc cake 8008: dev enp0s13 root refcnt 2 bandwidth 900Kbit besteffort
		dual-srchost nat rtt 100.0ms raw 
qdisc ingress ffff: dev enp0s13 parent ffff:fff1 ---------------- 
qdisc fq_codel 0: dev ifb0 root refcnt 2 limit 10240p flows 1024 		
quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc cake 8009: dev ifb4enp0s13 root refcnt 2 bandwidth 1900Kbit 		
besteffort dual-dsthost nat rtt 100.0ms raw 
-------8<--------

Using bittorrent, bmon on the gateway reports:
		RX bps 		RXpps	TX bps		
TXpps
enp0s14		19.25KiB	219	232.51KiB	184
enp0s13		393.36KiB	304	20.25KiB	220

In both cases the ingress rate limit on the WAN interface (enp0s13) is
not obeyed. I verified these data by using tcpdump and doing an IO-
Graph with wireshark.

Looking forward to your feedback,
George

  parent reply	other threads:[~2016-10-28  1:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1477497601.28053.cake@lists.bufferbloat.net>
2016-10-27  0:10 ` G. Amanakis
2016-10-27  0:16   ` G. Amanakis
2016-10-27  6:41     ` Sebastian Moeller
2016-10-27 16:42       ` Noah Causin
2016-10-28  1:34     ` Georgios Amanakis [this message]
2016-10-28  7:45       ` Sebastian Moeller
     [not found] <mailman.1.1477670401.20617.cake@lists.bufferbloat.net>
2016-10-30 16:43 ` Georgios Amanakis
2016-10-30 19:27   ` Sebastian Moeller
     [not found] <1462124589.1190968.1481310707746.ref@mail.yahoo.com>
2016-12-09 19:11 ` George Amanakis
2016-12-10 19:33   ` Benjamin Cronce

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=1477618454.22786.3.camel@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