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

Spot runaway systemd services without playing hide and seek

🧩 The Challenge

Dealing with a server that feels like it’s grinding to a halt because a background service is thrashing the CPU, but you have no clue which unit is actually responsible. I’ve spent way too many nights digging through top trying to map random PIDs back to specific systemd slices.

💡 The Fix

Use the systemd-cgtop tool to get a live, tree-structured view of resource consumption by unit. It’s like top, but it actually respects the hierarchy you built.

systemd-cgtop

⚙️ Why It Works

This utility hooks into the kernel cgroup accounting to show you exactly how much CPU, memory, and IO each service and slice is pulling in real-time. It beats trying to correlate PIDs manually when you have fifty services fighting for the same resources.

🚀 Pro-Tip: Keep an eye on the IO column if the server load is high but the CPU usage looks totally fine.

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