MikroTik CCR2004 Ping Spikes and CPU Usage - Seeking Community Insights
Hello MikroTik community! I’m seeking some help identifying some recent ping spikes and CPU usage increases on my CCR2004-16G-2S+
Here’s a quick summary:
Normal Ping: I typically enjoy a fantastic 5 ms ping to Google, indicating a healthy network overall.
Ping Spikes: However, when one of my machines is processing a network heavy workload (its a machine i am hosting). Machines experience ping spikes, reaching around 30-50 ms.
CPU Usage: During these spikes, the MikroTik CCR2004-16G-2S+ CPU utilization jumps to 50-60%.
Troubleshooting:
Bandwith Limits: I added inbound and outbound bandwidth limit (400M/400M of a 1G/1G connection) on the machine causing the issue. This calmed down the cpu spikes a bit and has avoided connection saturation, but further optimizations might be needed.
Desired Outcome:
My goal is to minimize ping spikes and maintain overall network stability, even with the rental’s high bandwidth activities.
Community Questions:
Traffic Shaping: Based on my current configuration, what advanced traffic shaping approaches would you recommend?
Queue Optimization: Any specific queue settings adjustments for handling spikes from the rental?
Potential Bottlenecks: Are there any known areas in the CCR2004 setup that might be causing these spikes?
General Optimization Tips: Any additional suggestions for maximizing router performance and minimizing ping fluctuations?
I’m grateful for any insights and guidance the community can offer!
Additional Information:
Router model: MikroTik CCR2004-16G-2S+
RouterOS version: Running 7.10
/queue simple print
Flags: X - disabled, I - invalid; D - dynamic
0 name=“renter_traffic_limit” target=192.168.200.0/24 parent=none packet-marks=renter_traffic
priority=8/8 queue=pcq-upload-default/pcq-download-default limit-at=0/0 max-limit=400M/400M
burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s bucket-size=0.1/0.1
1 name=“200-net-limit” target=192.168.200.0/24 parent=none packet-marks=“” priority=7/7
queue=pcq-upload-default/pcq-download-default limit-at=0/0 max-limit=950M/950M
burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s bucket-size=0.1/0.1
/queue tree print
Flags: X - disabled, I - invalid
/ip firewall mangle
add action=mark-packet chain=postrouting dst-address=104.x.x.x new-packet-mark=renter_traffic
passthrough=yes
add action=mark-packet chain=prerouting new-packet-mark=renter_traffic passthrough=yes
src-address=104.x.x.x
add action=mark-packet chain=prerouting new-packet-mark=high_priority_traffic passthrough=yes
src-address=192.168.88.0/24
add action=mark-packet chain=postrouting dst-address=192.168.88.0/24 new-packet-mark=
high_priority_inbound_traffic passthrough=yes