Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Loganaden Velvindron <loganaden@gmail.com>
To: moeller0 <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] fq_codel on 3g network in Mauritius
Date: Sat, 23 Jul 2016 22:59:43 +0400	[thread overview]
Message-ID: <CAOp4FwQuHHq-aX+sBRV7F8oF5y2p6m2gb-kFE+5p3+9JH7H4Cg@mail.gmail.com> (raw)
In-Reply-To: <CAOp4FwR-s29C6kbEt-OutZEezXSwVritTZL7bL74+eOH54QZnQ@mail.gmail.com>

After going through:

https://tools.ietf.org/html/draft-ietf-aqm-fq-codel-06

I think that I should remove the itarget and etarget, and set the
Interval rather to 500ms.



   The _interval_ parameter has the same semantics as CoDel and is used
   to ensure that the minimum sojourn time of packets in a queue used as
   an estimator by the CoDel control algorithm is a relatively up-to-
   date value.  That is, CoDel only reacts to delay experienced in the
   last epoch of length interval.  It SHOULD be set to be on the order
   of the worst-case RTT through the bottleneck to give end-points
   sufficient time to react.

   The default interval value is 100 ms.

The default interval value is not suited for my 3g connection where
the worse-case RTT is much higher.



On Sat, Jul 23, 2016 at 10:36 PM, Loganaden Velvindron
<loganaden@gmail.com> wrote:
>>         It seems the initial burst like behavior from the earlier test was a false positive; these test are still not beautiful, but at least they do not indicate that HTB+fq_codel as configured on your system do not suffer from uncontrolled bursty-ness. Unfortunately, I have no real insight or advice to offer how to improve your situation (short f setting the shaper rates considerably lower).
>>         BTW, “tc -d qdisc” and “tc -s disc” give a bit more information, and “tc class show dev eth1” and “tc class show dev ifb4eth1” will also offer more detail about your setup.
>>
>>
>> Best Regards
>>         Sebastian
>>
>>
>>
>
> tc -d qdisc:
>
> qdisc fq_codel 0: dev eth0 root refcnt 2 limit 1024p flows 1024
> quantum 300 target 5.0ms interval 100.0ms ecn
> qdisc htb 1: dev eth1 root refcnt 2 r2q 10 default 12
> direct_packets_stat 5 ver 3.17 direct_qlen 1000
> qdisc fq_codel 110: dev eth1 parent 1:11 limit 1001p flows 1024
> quantum 300 target 500.0ms interval 100.0ms
> qdisc fq_codel 120: dev eth1 parent 1:12 limit 1001p flows 1024
> quantum 300 target 500.0ms interval 100.0ms
> qdisc fq_codel 130: dev eth1 parent 1:13 limit 1001p flows 1024
> quantum 300 target 500.0ms interval 100.0ms
> qdisc ingress ffff: dev eth1 parent ffff:fff1 ----------------
> qdisc mq 0: dev wlan0 root
> qdisc htb 1: dev ifb4eth1 root refcnt 2 r2q 10 default 10
> direct_packets_stat 0 ver 3.17 direct_qlen 32
> qdisc fq_codel 110: dev ifb4eth1 parent 1:10 limit 1001p flows 1024
> quantum 300 target 500.0ms interval 100.0ms ecn
>
> tc -s qdisc:
>
> qdisc fq_codel 0: dev eth0 root refcnt 2 limit 1024p flows 1024
> quantum 300 target 5.0ms interval 100.0ms ecn
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
>   maxpacket 256 drop_overlimit 0 new_flow_count 0 ecn_mark 0
>   new_flows_len 0 old_flows_len 0
> qdisc htb 1: dev eth1 root refcnt 2 r2q 10 default 12
> direct_packets_stat 5 direct_qlen 1000
>  Sent 23456195 bytes 109776 pkt (dropped 0, overlimits 86210 requeues 0)
>  backlog 0b 4p requeues 0
> qdisc fq_codel 110: dev eth1 parent 1:11 limit 1001p flows 1024
> quantum 300 target 500.0ms interval 100.0ms
>  Sent 14760 bytes 164 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
>   maxpacket 256 drop_overlimit 0 new_flow_count 163 ecn_mark 0
>   new_flows_len 1 old_flows_len 0
> qdisc fq_codel 120: dev eth1 parent 1:12 limit 1001p flows 1024
> quantum 300 target 500.0ms interval 100.0ms
>  Sent 23440300 bytes 109600 pkt (dropped 115, overlimits 0 requeues 0)
>  backlog 5816b 4p requeues 0
>   maxpacket 1454 drop_overlimit 0 new_flow_count 15749 ecn_mark 0
>   new_flows_len 0 old_flows_len 1
> qdisc fq_codel 130: dev eth1 parent 1:13 limit 1001p flows 1024
> quantum 300 target 500.0ms interval 100.0ms
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
>   maxpacket 256 drop_overlimit 0 new_flow_count 0 ecn_mark 0
>   new_flows_len 0 old_flows_len 0
> qdisc ingress ffff: dev eth1 parent ffff:fff1 ----------------
>  Sent 190858989 bytes 149884 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
> qdisc mq 0: dev wlan0 root
>  Sent 194287835 bytes 153002 pkt (dropped 0, overlimits 0 requeues 7)
>  backlog 0b 0p requeues 7
> qdisc htb 1: dev ifb4eth1 root refcnt 2 r2q 10 default 10
> direct_packets_stat 0 direct_qlen 32
>  Sent 192953486 bytes 149877 pkt (dropped 0, overlimits 41505 requeues 0)
>  backlog 0b 0p requeues 0
> qdisc fq_codel 110: dev ifb4eth1 parent 1:10 limit 1001p flows 1024
> quantum 300 target 500.0ms interval 100.0ms ecn
>  Sent 192953486 bytes 149877 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
>   maxpacket 1454 drop_overlimit 0 new_flow_count 16778 ecn_mark 0
>   new_flows_len 1 old_flows_len 2
>
>
> tc class show dev eth1
> class htb 1:11 parent 1:1 leaf 110: prio 1 rate 128Kbit ceil 100Kbit
> burst 1600b cburst 1600b
> class htb 1:1 root rate 300Kbit ceil 300Kbit burst 1599b cburst 1599b
> class htb 1:10 parent 1:1 prio 0 rate 300Kbit ceil 300Kbit burst 1599b
> cburst 1599b
> class htb 1:13 parent 1:1 leaf 130: prio 3 rate 50Kbit ceil 284Kbit
> burst 1600b cburst 1599b
> class htb 1:12 parent 1:1 leaf 120: prio 2 rate 50Kbit ceil 284Kbit
> burst 1600b cburst 1599b
> class fq_codel 110:188 parent 110:
> class fq_codel 120:3d6 parent 120:
>
>
> tc class show dev ifb4eth1:
> class htb 1:10 parent 1:1 leaf 110: prio 0 rate 19600Kbit ceil
> 19600Kbit burst 1597b cburst 1597b
> class htb 1:1 root rate 19600Kbit ceil 19600Kbit burst 1597b cburst 1597b
> class fq_codel 110:2f1 parent 110:
> class fq_codel 110:330 parent 110:
>
> I changed the target from 350ms to 500ms for both ingress and egree,
> and the throughput seem to be better:
>
> http://www.dslreports.com/speedtest/4515961

  reply	other threads:[~2016-07-23 18:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19  4:29 Loganaden Velvindron
2016-07-19  8:09 ` Jonathan Morton
2016-07-19 10:16   ` moeller0
     [not found]     ` <CAOp4FwQs9-PF=V5zDDMVj_38qmziKkeZECTyX1e8EfChtGm8bA@mail.gmail.com>
     [not found]       ` <7ECE7E7A-0310-4DC4-8AC9-29B0F1F2E383@gmx.de>
2016-07-23 18:36         ` Loganaden Velvindron
2016-07-23 18:59           ` Loganaden Velvindron [this message]
2016-07-24  5:53             ` Loganaden Velvindron
2016-07-24  6:12               ` Loganaden Velvindron
2016-07-24  7:03                 ` Loganaden Velvindron
2016-07-24  8:27                   ` moeller0
2016-07-24  8:43                     ` Loganaden Velvindron
2016-07-24 10:53               ` moeller0
2016-07-24 11:28                 ` Jonathan Morton
2016-07-24 14:40                   ` moeller0
2016-07-24 16:18                     ` Jonathan Morton
2016-07-24 17:13                     ` Loganaden Velvindron
2016-07-24 17:21                       ` moeller0
2016-07-24 19:43                         ` Loganaden Velvindron
2016-07-25  4:13                           ` Loganaden Velvindron
2016-07-26 21:10                             ` Loganaden Velvindron
2016-07-30  3:45                               ` Loganaden Velvindron
2016-07-30 13:04                                 ` Mario Ferreira
2016-07-30 13:48                                   ` Loganaden Velvindron
2016-07-30 14:07                                     ` Mario Ferreira
2016-08-03 18:52                               ` Loganaden Velvindron
2016-08-03 19:48                                 ` David Lang
2016-07-19 17:13   ` Loganaden Velvindron

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=CAOp4FwQuHHq-aX+sBRV7F8oF5y2p6m2gb-kFE+5p3+9JH7H4Cg@mail.gmail.com \
    --to=loganaden@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --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