Am 16.09.2019 um 14:08 schrieb Toke Høiland-Jørgensen:
Sebastian Gottschall <[email protected]> writes:

after we found out serious out of memory issues on smaller embedded
devices (128 mb ram) we made some benchmarks with different schedulers
with the result that cake takes a serious amount of memory. we use the
out of tree cake module and we use it class based since we have complex
methods of doing qos per interface, per mac addresse or even per
ip/network. so its not just simple cake on a single interface solution.
we made some benchmarks with different schedulers. does anybody have a
solution for making that better?

HTB/FQ_CODEL ------- 62M
HTB/SFQ ------- 62M
HTB/PIE ------- 62M
HTB/FQ_CODEL_FAST ------- 67M
HTB/CAKE -------111M

HFSC/FQ_CODEL_FAST ------- 47M
HTB/PIE ------- 49M
HTB/SFQ ------- 50M
HFSC /FQ_CODEL ------- 52M
HFSC/CAKE -------109M
How are you measuring the memory usage, and what is your full config for
each setup? :)
me? nothing. i requested this test from a reporter and he uses just free / top. so there is a error tollerance.

but it shows a significant difference between cake and fq_codel etc. cake is doing a OOM at the end

for the full report including config screenshots see this https://svn.dd-wrt.com/ticket/6798#comment:14. it shows also the qos setup which i can use to reproduce and to print out the full tc ruleset if required (which it surelly is for you). if you want i will recreate this setup and send the tc rules on this list


-Toke


_______________________________________________
Cake mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/cake

Reply via email to