HTB: quantum of class 10001 is big. Consider r2q change

[saschaarthur]

[985942.638339] HTB: quantum of class 10001 is big. Consider r2q change. [985942.639499] HTB: quantum of class 10010 is big. Consider r2q change. [985942.640407] HTB: quantum of class 10020 is big. Consider r2q change. [985942.641699] HTB: quantum of class 10030 is big. Consider r2q change. [985942.678996] HTB: quantum of class 20001 is big. Consider r2q change.

When restarting wondershaper system unit, any idears how to solve it?

Already tried to raise and lower the constant there, but doesnt help at all...

[slrslr]

I have seen this:

HTB: quantum of class 10001 is big. Consider r2q change.
HTB: quantum of class 10020 is big. Consider r2q change.
u32 classifier
    Performance counters on
    input device check on
    Actions configured
Mirror/redirect action on
HTB: quantum of class 20001 is big. Consider r2q change.
kauditd_printk_skb: 32 callbacks suppressed

$ wondershaper -v Version 1.4.1 Manjaro/Arch Linux

These messages appear also when i try to increase/decrease the limit using wondershaper. Which alternative BW limitting app i can use? https://alternativeto.net/software/wondershaper/?platform=linux / https://github.com/cryzed/TrafficToll

[slrslr]

Should the htb value be changed?

https://documentation.clearos.com/content:en_us:kb_troubleshooting_kernel-_htb-_quantum_of_class_10001_is_big._consider_r2q_change

But how/how to calculate proper value?

$ grep -ni htb /usr/bin/wondershaper

133:# install root HTB
135:tc qdisc add dev "$IFACE" root handle 1: htb default 20;
141:  tc class add dev "$IFACE" parent 1: classid 1:1 htb \
149:  tc class add dev "$IFACE" parent 1:1 classid 1:10 htb \
158:  tc class add dev "$IFACE" parent 1:1 classid 1:20 htb \
166:  tc class add dev "$IFACE" parent 1:1 classid 1:30 htb \
249:  tc qdisc add dev "$IFB" root handle 2: htb;
250:  tc class add dev "$IFB" parent 2: classid 2:1 htb rate "${DSPEED}kbit";

@magnific0 @saimonn ...

[saimonn]

This is a warning message and doesn't mean wondershaper is not functional.

The quantum value of 6000 is arbitrary in wondershaper code (if I remember it was good for a ~100Mbit connection), and could be lowered or increased depending on your actual bandwith. It should also be possible to remove it completely from here, and let the kernel use the default value of rate/r2q (with r2q=10 by default)

[jzvikart]

@saimonn How would you recommend to adjust this parameter? I.e. what would be the optimal value?

Also, what are the potential side effects and limitations of not adjusting it?