A no-nonsense order of operations for finding what’s actually slowing a Linux box down — CPU, memory, disk, I/O, or something noisier.
“The server is slow” is a symptom, not a diagnosis. The trick is to narrow it down in the right order so you don’t waste an hour chasing the wrong resource. Here’s the checklist we actually use.
1. Is it CPU, memory, disk, or I/O?
Start broad. Look at load average relative to core count — a load of 8 on an 8-core box is fully saturated; on a 2-core box it’s an emergency. Then check whether memory pressure is forcing swap, and whether a disk is near full or saturated with I/O wait.
Load average vs cores: > 1× per core means saturation, > 2× means overloaded.
Memory: high swap usage means you’re out of RAM and paging to disk — everything gets slow.
Disk: a full disk (or one stuck in I/O wait) stalls writes for every process on the box.
2. Which process is responsible?
Once you know the resource, find the culprit. Sort processes by the resource that’s saturated — CPU or memory — and look at the top few. A runaway worker, a stuck cron job, or a memory-leaking app usually stands out immediately.
3. Did something change?
Most “sudden” slowness has a cause: a deploy, a traffic spike, a log file that stopped rotating and filled the disk, or a service that crashed and is restarting in a loop. Correlate the slowdown with what happened around the same time.
The fastest path to a fix is almost always “what changed?” — not “what’s the metric?”
4. The shortcut
This is exactly the loop Opservo automates. It watches CPU, memory, disk, load and I/O on every server, tells you in plain English which one is the problem and which process is responsible, and ties the slowdown to what changed — a deploy, a crash, a log that stopped rotating. Instead of running this checklist by hand at 3am, you open the server and it’s already on the screen.
Originally published on the Opservo blog — Opservo is the AI ops engineer for teams without an SRE. Free for 2 servers → https://getopservo.com/welcome
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.