General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] weird problem WRT1200 + CAKE on OpenWrt 18.06.2
Date: Wed, 31 Jul 2019 09:58:03 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1907310949260.16521@uplift.swm.pp.se> (raw)


Hi,

I've been running openwrt 18.06.2 for a long time on my WRT1200AC, with 
CAKE, and everything has been great. I always got A+ in dslreports for 
bufferbloat. I have a 250/100 ETTH connection (IP over ethernet native, no 
PPPoE, no PON).

I noticed some intermittent network stuttering issues I wanted to diagnose 
last week, so I started looking into this. When doing the test I get 
+100ms spikes in the downstream direction when I run CAKE. If I instead 
switch to FQ_CODEL I do not see these spikes. As a matter of fact, if I 
set my downstream to 300 when running cake and let my ISP handle the 
buffering then I get an average of 5-10ms worth of buffering with no 
spikes. My ISP isn't bloated in that direction.

# tc qdisc show dev eth1.2
qdisc cake 801f: root refcnt 2 bandwidth 100Mbit diffserv3 triple-isolate nonat nowash no-ack-filter split-gso rtt 100.0ms noatm overhead 22
qdisc ingress ffff: parent ffff:fff1 ----------------

tc qdisc show dev ifb4eth1.2
qdisc cake 8020: root refcnt 2 bandwidth 240Mbit diffserv3 triple-isolate nonat nowash no-ack-filter split-gso rtt 100.0ms noatm overhead 22

http://www.dslreports.com/speedtest/52542158 is the result I get with 
above settings.

http://www.dslreports.com/speedtest/52542263 is the result with FQ_CODEL:

# tc qdisc show dev eth1.2
qdisc htb 1: root refcnt 2 r2q 10 default 18 direct_packets_stat 0 direct_qlen 1000
qdisc fq_codel 120: parent 1:12 limit 1001p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 130: parent 1:13 limit 1001p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 110: parent 1:11 limit 1001p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc ingress ffff: parent ffff:fff1 ----------------

# tc qdisc show dev ifb4eth1.2
qdisc htb 1: root refcnt 2 r2q 10 default 18 direct_packets_stat 0 direct_qlen 32
qdisc fq_codel 120: parent 1:12 limit 1001p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 130: parent 1:13 limit 1001p flows 1024 quantum 300 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 110: parent 1:11 limit 1001p flows 1024 quantum 500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn

How do I diagnose this further?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

             reply	other threads:[~2019-07-31  7:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31  7:58 Mikael Abrahamsson [this message]
2019-08-08 20:33 ` Toke Høiland-Jørgensen
2019-08-09  4:21   ` Mikael Abrahamsson
2019-08-09  4:35     ` David Lang
2019-08-09  8:38     ` Toke Høiland-Jørgensen
2019-08-09 17:44     ` Rosen Penev
2019-08-09 17:49       ` Sebastian Moeller
2019-08-09 17:53         ` Jonathan Morton
2019-08-09 17:58           ` Sebastian Moeller
2019-08-09 17:57         ` Rosen Penev

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1907310949260.16521@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@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