From: Pete Heist <pete@heistp.net>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] Cake memory usage after 1TB
Date: Thu, 24 Jun 2021 15:06:00 +0200 [thread overview]
Message-ID: <3d529e0b78ef8ea54021d8f8e93285e9a474cba1.camel@heistp.net> (raw)
I'm using Cake on an EdgeRouter-X at a site that does around 50-
100GB/day, and we're quite happy with it so far. Egress and ingress
stats are below after ~1TB download and ~100GB upload.
I use "memlimit 8M", and noticed that it's reporting 8389696 bytes used
on egress, which is at the maximum (slightly over actually). Around 6M
is used on ingress. Should I then raise these limits, or is it normal
for it to settle in around the maximum over time?
Pete
Egress:
-------
qdisc cake 8008: dev eth4 root refcnt 2 bandwidth 8Mbit diffserv4 dual-
srchost nat nowash no-ack-filter split-gso rtt 100.0ms raw overhead 0
fwmark 0xf no-sce
Sent 102655686381 bytes 386831397 pkt (dropped 377557, overlimits
230324326 requeues 0)
backlog 0b 0p requeues 0
memory used: 8389696b of 8Mb
capacity estimate: 8Mbit
min/max network layer size: 42 / 1514
min/max overhead-adjusted size: 42 / 1514
average network hdr offset: 14
Bulk Best Effort Video Voice
thresh 500Kbit 8Mbit 4Mbit 2Mbit
target 36.3ms 5.0ms 5.0ms 9.1ms
interval 131.3ms 100.0ms 100.0ms 104.1ms
pk_delay 17.5ms 4.1ms 1.7ms 2.0ms
av_delay 4.5ms 232us 82us 382us
sp_delay 14us 23us 6us 7us
backlog 0b 0b 0b 0b
pkts 165781 324229040 61032588 1781545
bytes 45344666 98316181815 4518083349 291035866
way_inds 42 18492140 7782656 34167
way_miss 4289 6575635 77917 62650
way_cols 0 340 0 0
sce 0 0 0 0
marks 7 19542 1 0
drops 8 377528 15 6
ack_drop 0 0 0 0
sp_flows 0 2 0 1
bk_flows 0 1 0 0
un_flows 0 0 0 0
max_len 1514 1514 1514 1514
quantum 300 300 300 300
Ingress:
--------
qdisc cake 1: dev ifb4eth4 root refcnt 2 bandwidth 40Mbit diffserv4
dual-dsthost nat nowash no-ack-filter split-gso rtt 100.0ms raw
overhead 0 fwmark 0xf no-sce
Sent 1081750548776 bytes 839670608 pkt (dropped 1616216, overlimits
657093747 requeues 0)
backlog 0b 0p requeues 0
memory used: 6027328b of 8Mb
capacity estimate: 40Mbit
min/max network layer size: 60 / 1514
min/max overhead-adjusted size: 60 / 1514
average network hdr offset: 14
Bulk Best Effort Video Voice
thresh 2500Kbit 40Mbit 20Mbit 10Mbit
target 7.3ms 5.0ms 5.0ms 5.0ms
interval 102.3ms 100.0ms 100.0ms 100.0ms
pk_delay 2.0ms 6.5ms 692us 1.1ms
av_delay 248us 2.6ms 88us 139us
sp_delay 12us 16us 7us 6us
backlog 0b 0b 0b 0b
pkts 29132 682090182 155330794 3836716
bytes 25452377 850788764602 230875228776 2357107850
way_inds 3 37939194 21198287 71120
way_miss 9448 6525310 97141 51428
way_cols 0 107 0 0
sce 0 0 0 0
marks 0 206496 203 30
drops 30 1534636 80809 741
ack_drop 0 0 0 0
sp_flows 0 2 0 0
bk_flows 0 1 0 0
un_flows 0 0 0 0
max_len 1484 1514 1514 1514
quantum 300 1220 610 305
next reply other threads:[~2021-06-24 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 13:06 Pete Heist [this message]
2021-06-24 13:26 ` Pete Heist
2021-06-24 13:33 ` Dave Taht
2021-06-24 13:59 ` Toke Høiland-Jørgensen
2021-06-24 15:00 ` Pete Heist
2021-06-24 15:07 ` Sebastian Moeller
2021-06-24 15:20 ` Toke Høiland-Jørgensen
2021-06-24 15:25 ` Dave Taht
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=3d529e0b78ef8ea54021d8f8e93285e9a474cba1.camel@heistp.net \
--to=pete@heistp.net \
--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