Process & Resource Monitoring (Top/Htop/Ps/Systemd)

Stop staring at the CPU column wondering who is actually eating your cycles

🧩 The Challenge

Everyone thinks they know how to read top, but you’re probably ignoring the one metric that shows you which threads are actually fighting for the CPU. Sometimes the aggregate process view hides the fact that one runaway thread is killing your latency.

💡 The Fix

Switch your top view to show individual threads so you can see exactly which part of the application is pinning your cores. It’s the only way to catch developers who spawn too many threads for the available hardware.

top -H -p <PID>

⚙️ Why It Works

Adding the -H flag forces the process list to explode into individual threads. By pinning it to a specific PID with -p, you stop the noise of the rest of the OS and focus on the guilty party.

🚀 Pro-Tip: Hit ‘1’ while inside top to see the per-core breakdown of that thread usage.

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