From: <jmarks2@gmail.com>
To: <cake@lists.bufferbloat.net>
Subject: [Cake] Trouble getting decent performance with CAKE
Date: Tue, 26 Jan 2021 18:21:58 -0600 [thread overview]
Message-ID: <005701d6f442$6d620e90$48262bb0$@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1730 bytes --]
Dear CAKE experts,
I write for your help in getting CAKE to perform on my router as I
understand it should.
I replaced my aging Asus home router with a Ubiquiti Edgerouter 4
specifically so I could take advantage of the port of CAKE to it.
I am in the US, with VDSL2 service provided by AT&T at 100/20. I now have
all unfiltered traffic delivered by the AT&T modem to the eth0 port on the
router.
My desktop runs Windows. So, to take advantage of flent to quantify CAKE
performance, I stood up a Linux Mint VM and ran flent rrul tests before CAKE
installation, and after.
The first attached datafile, labeled qdisc pfifo fast, is the performance
before CAKE. The other file, called 20/95 ack filtered bridged ptm, is my
latest attempt with configuring CAKE flags.
My major issue is with Ingress. Egress seems fine.
For ingress, I see very little difference between performances with and
without CAKE. And the overall throughput is far less than 100 mbit.
The queuing disciplines on the router are:
jeremymarks@ubnt:~$ sudo tc qdisc show
qdisc cake 1: dev eth0 root refcnt 2 bandwidth 20Mbit besteffort
dual-srchost nat nowash ack-filter split-gso rtt 100.0ms ptm overhead 22
no-sce
qdisc ingress ffff: dev eth0 parent ffff:fff1 ----------------
qdisc pfifo_fast 0: dev imq0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0
1 1 1 1 1 1 1 1
qdisc cake 2: dev ifb0 root refcnt 2 bandwidth 95Mbit besteffort
dual-dsthost nat nowash ingress ack-filter split-gso rtt 100.0ms ptm
overhead 22 no-sce
I must be making a major mistake in configuring CAKE.
I would be grateful for any help or advice in getting this amazing program
to work as it should.
Many thanks for any help.
Jeremy
[-- Attachment #1.2: Type: text/html, Size: 5552 bytes --]
[-- Attachment #2: rrul-2021-01-24T110301.456648.qdisc_pfifo_fast.flent.gz --]
[-- Type: application/x-gzip, Size: 121758 bytes --]
[-- Attachment #3: rrul-2021-01-24T162210.973709.20_95_ack_filtered_bridged-ptm.flent.gz --]
[-- Type: application/x-gzip, Size: 119863 bytes --]
next reply other threads:[~2021-01-27 0:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 0:21 jmarks2 [this message]
2021-01-27 2:04 ` xnor
2021-01-27 5:19 ` Dave Taht
2021-01-27 17:49 ` jmarks2
2021-01-27 17:51 ` Dave Taht
2021-01-27 18:25 ` Jeremy Marks
2021-01-28 17:17 ` xnor
[not found] ` <00ba01d6f5a1$450d07f0$cf2717d0$@gmail.com>
2021-01-28 22:00 ` xnor
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='005701d6f442$6d620e90$48262bb0$@gmail.com' \
--to=jmarks2@gmail.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