Linux Load Average Explained: uptime, CPU Cores and When to Worry

linux load average - custom-loadavg-featured.png

Load average confuses newcomers because it is not a CPU percentage. It estimates how many tasks are runnable or waiting (including on disk), smoothed over 1, 5, and 15 minutes — the numbers uptime prints after the time.

Tools: htop guide,
top, iostat, vmstat.

What the Three Numbers Mean

They are exponentially damped moving averages of runnable + uninterruptible tasks.

1 5 15 min
not CPU%

uptime Quick Check

First command on a slow SSH session.

bashuptime
uptime
uptime
load triple

Compare With top or htop

See whether CPUs are busy, idle, or waiting on disk.

bashcores
nproc
htop   # or: top
htop
running

Rule of Thumb: Cores

On a 4-vCPU VM, sustained load above ~4 often means saturation; context matters for I/O-heavy workloads.

load vs nproc
vCPU

High Load, Low CPU: iowait

Disk or NFS bottlenecks inflate load while CPU looks idle — check wa in vmstat.

bashvmstat
vmstat 1 5
iowait
disk

What to Do Next

Find the hot process, fix queries, add RAM/disk throughput, or scale horizontally.

triage
scale

Monitoring

Alert on trends, not a single spike during apt upgrade.

TipPair load alerts with disk latency and memory — load alone is ambiguous.
alerting
Prometheus

Quick Reference

  • uptime → compare load to nproc
  • High load + high wa → disk I/O
  • Use htop to find the process

Related tutorials

Diagrams are original illustrations by Gnome IT Solutions. Tutorial text © Gnome IT Solutions.