Netgear R7800 Stuck at 110 Mbps with SQM CAKE

Thanks for the advice.

No, but I did now (reload_config).

I did something like this on 21.02:

echo 25 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 10 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor	

I didn't verify that it was set to ondemand, however.

I also tried @ACwifidude's build and had similar results on hardware accelerated (HW) fc_codel.

No SQM, ACwifidude's build:

the best for latency is somewhere around 200-220Mbit.

These are my settings in local startup and I reboot every time I changed something. I also changed to "Bootstrap" from their default material theme. Cleared out everything when I did the firmware install (no config carryover).

# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 600000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 25 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 10 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor	
uci set irqbalance.irqbalance.enabled=1; uci set network.globals.packet_steering=1; uci commit
modprobe nss-ifb

ip link set up nssifb

# Shape ingress traffic with chained NSSFQ_CODEL
tc qdisc add dev nssifb root handle 1: nsstbl rate 220Mbit burst 1Mb
tc qdisc add dev nssifb parent 1: handle 10: nssfq_codel limit 10240 flows 1024 quantum 1514 target 5ms interval 100ms set_default

# Shape egress traffic with chained NSSFQ_CODEL
tc qdisc add dev eth0 root handle 1: nsstbl rate 11.4Mbit burst 1Mb
tc qdisc add dev eth0 parent 1: handle 10: nssfq_codel limit 10240 flows 1024 quantum 1514 target 5ms interval 100ms set_default
exit 0

I might go back to 21.02 and try max performance and see if it can keep up with CAKE. I'm not hopeful based on my other results. There are 3 devices hardwired to the r7800 but I don't think any of them are causing problems. Wifi remains off while I test SQM.

I ran top during one of the tests and CPU remained >40% idle but I didn't get a per-core breakdown.