Performance Tuning & Kernel Parameters (Sysctl)

Quit letting your server panic over weird ARP traffic

🧩 The Challenge

Dealing with a massive jump in local network traffic and watching your CPU spike because the kernel is busy trying to resolve ARP requests that make no sense. It’s infuriating when your load balancer or firewall just decides to drop off the grid because the ARP cache got overwhelmed by garbage.

💡 The Fix

You need to tell the kernel to chill out and stop being so aggressive about validating every single ARP packet it sees. Tweak your sysctl settings to prevent cache exhaustion and stop the noise from killing your throughput.

sysctl -w net.ipv4.neigh.default.gc_thresh1=1024
sysctl -w net.ipv4.neigh.default.gc_thresh2=2048
sysctl -w net.ipv4.neigh.default.gc_thresh3=4096

⚙️ Why It Works

These settings adjust the garbage collection thresholds for the neighbor table, essentially giving the kernel more breathing room before it starts aggressively dropping entries to manage memory. Increasing these limits keeps your connection table stable even when the local network environment gets chaotic.

🚀 Pro-Tip: Throw these into a file in /etc/sysctl.d/ instead of doing it live, or they’ll vanish the second you reboot.

Linux Tips & Tricks | © ngelinux.com | 11/9/2026