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

Stop playing Where’s Waldo with processes

🧩 The Challenge

Hunting down a process by name when you have fifty identical threads running is a special kind of hell. I’ve wasted way too many minutes squinting at htop trying to figure out which specific thread is actually hammering the disk.

💡 The Fix

Use pgrep with the -a flag to pull the full command line arguments, or better yet, use ps with custom output columns to see exactly what’s hitting your hardware. You’ll save yourself the headache of blindly guessing which PID to attach to.

ps -eo pid,ppid,cmd,%mem,%cpu --sort=-%cpu | head -n 10

⚙️ Why It Works

This command forces ps to display only the columns that matter, sorted by the biggest CPU offenders, so you stop wasting screen real estate on idle processes. It strips away the noise and dumps the data directly into your terminal in a readable format.

🚀 Pro-Tip: Stick | head -n 10 on the end so you don’t get a wall of text filling your entire scrollback buffer.

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