Find what is using it
Tools > Profile shows which process uses the CPU. Firewall, queuing, DNS and management traffic each point to a different fix.
Firewall rule order
Put accept rules for established and related connections at the top of the filter chain so most packets are handled by the first rule. Long lists of rules checked for every packet cost CPU.
Too many simple queues
Thousands of simple queues checked in order are expensive. PCQ-based queues or queue trees scale better for large customer counts.
FastTrack and its trade-off
FastTrack lets established traffic skip most processing and saves a lot of CPU. The trade-off is that fast-tracked traffic bypasses simple queues and mangle, so plan speed limits accordingly.
Open services and attacks
An open DNS resolver or an exposed Winbox and API port can be abused from the internet and push CPU to 100 percent. Block them on the WAN side.
See it working
Open a live demo or talk to the Sweet Billing team about your setup.
