Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Loganaden Velvindron <loganaden@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] fq_codel on 3g network in Mauritius
Date: Tue, 19 Jul 2016 21:13:45 +0400	[thread overview]
Message-ID: <CAOp4FwS6R1jg+p-E6RpgzW5RzjfQsnZVnyN5eUTToX2m+CvdJA@mail.gmail.com> (raw)
In-Reply-To: <66C89432-6E70-422F-A638-7522BF233707@gmail.com>

On Tue, Jul 19, 2016 at 12:09 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 19 Jul, 2016, at 07:29, Loganaden Velvindron <loganaden@gmail.com> wrote:
>>
>> I've been playing with fq_codel on 3g internet connection. the 3g
>> internet box has no bridge mode, and just forwards every packet to the
>> Openwrt router.
>>
>> Here are the results without:
>> http://www.dslreports.com/speedtest/4470186
>>
>> And here is the result with fq_codel on and 300 ms target latency:
>>
>> http://www.dslreports.com/speedtest/4470286
>>
>> Is there anything that could be done to get the rating up to A+ by
>> tweaking the code ?
>
> You say fq_codel, rather than Cake.  Presumably it is paired with some sort of shaper, such as HTB?  This is important, because I think the shaper is influencing part of your results.
>
> On downstream, you have one high latency sample (750ms) in the middle of a series of reasonable ones (250ms).  This implies a momentary glitch in your connection, which isn’t unusual with wireless links.  Re-measuring might eliminate it.
>
> On upstream, you have two very high latency samples at the *beginning* of the run, which then clear out to approximately the baseline latency.  This is a classic sign that your shaper is letting a burst of traffic through before actually starting to control it, which is typical behaviour for token-bucket shapers.  That initial burst collects in the dumb queue of your 3G modem and takes time to drain away.
>
> Cake uses a shaper carefully designed to *not* burst in that manner, while still maintaining full throughput regardless of timer resolution and latency.  Using Cake instead of fq_codel+HTB will therefore probably improve your upload characteristics.
>

here's the output from tc:

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 0 direct_qlen 1000
qdisc fq_codel 110: dev eth1 parent 1:11 limit 1001p flows 1024
quantum 300 target 300.0ms interval 100.0ms
qdisc fq_codel 120: dev eth1 parent 1:12 limit 1001p flows 1024
quantum 300 target 300.0ms interval 100.0ms
qdisc fq_codel 130: dev eth1 parent 1:13 limit 1001p flows 1024
quantum 300 target 300.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 direct_qlen 32
qdisc fq_codel 110: dev ifb4eth1 parent 1:10 limit 1001p flows 1024
quantum 300 target 300.0ms interval 100.0ms ecn

I will give CAKE a try. However, I'm not sure if there's enough space
(4mb NAND flash) on the tp-link wr841nd for sqm-qos. I will need to
get another box like the tp-link archer c7.

      parent reply	other threads:[~2016-07-19 17:13 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
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 [this message]

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=CAOp4FwS6R1jg+p-E6RpgzW5RzjfQsnZVnyN5eUTToX2m+CvdJA@mail.gmail.com \
    --to=loganaden@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