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

Stop your custom systemd services from acting like black holes

🧩 The Challenge

Dealing with a service that spins up a dozen child processes is a nightmare when you have no idea which pid belongs to what, especially when they start dying off randomly. You run systemctl status and get a generic list that doesn’t tell you anything about actual resource consumption.

💡 The Fix

Use the cgroup-aware tools built right into systemd to see the entire process tree and its aggregate resource usage at a glance. It saves you from digging through top or htop trying to map parent-child relationships manually.

systemd-cgtop

⚙️ Why It Works

This utility monitors the control groups directly, giving you a live breakdown of CPU and memory pressure per unit instead of just flat process IDs. It filters out the noise so you can see if your web server’s children are the ones actually leaking RAM.

🚀 Pro-Tip: Hit ‘k’ to change the sort order to memory usage if you’re hunting down a memory leak in a multi-process app.

Linux Tips & Tricks | © ngelinux.com | 8/14/2026