disk I/O bottleneck: how to confirm with iostat

TL;DR

iostat confirms a disk bottleneck with three numbers: await (how long I/O takes), util (how busy the device is), and avgqu-sz (how deep the queue is). High await plus high util means the disk is the bottleneck; high await with low util means something else is slow. Run it during the slow period, compare against the device's known baseline, and you will know in a minute.

The query

disk I/O bottleneck: how to confirm with iostat

Use this when

• A server is slow and disk is suspected
• Distinguishing I/O wait from CPU or memory pressure
• Quantifying whether storage keeps up with the workload
• Before and after storage changes

Steps

Step 1: Run iostat during the slow period

Collect extended device stats over a representative window while the problem is happening. Idle-period numbers prove nothing; you need the stats from when it hurts. Expected output: per-device stats captured under load.

Step 2: Read await, util, and queue depth together

The key columns: await (average ms per I/O), %util (device busy percentage), avgqu-sz (average queue length). %util near 100 with rising await and queue depth is a saturated device. High await with low util suggests the slowness is elsewhere (or tiny serial I/Os). Expected output: a verdict: disk-bound, not-disk-bound, or mixed.

Step 3: Check which pattern dominates: reads vs writes

Look at read vs write throughput and IOPS. Write-heavy saturation suggests different fixes (write caching, faster media) than read-heavy (read cache, more IOPS). The r/s and w/s columns split the story. Expected output: the workload characterized as read-heavy, write-heavy, or mixed.

Step 4: Correlate with application symptoms

Match the iostat window to application metrics: request latency spikes, I/O wait in top, slow query logs. The disk numbers confirm the bottleneck only when they line up with the user-visible symptom in time. Expected output: time-correlated evidence that disk I/O is (or is not) the cause of the slowdown.

Step 5: Compare against baseline

A device at 80% util might be normal for your workload or a crisis; only the baseline tells you. Keep historical iostat snapshots from healthy periods. Without a baseline, "high" is just a feeling. Expected output: current numbers judged against known-good numbers, with the delta quantified.

Not for when

• Fixing the storage itself (provisioning, tuning)
• Network filesystem performance (different tools)
• Database-level I/O analysis (query plans first)

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_B8tGvkhBL0HecIEeF5vp6g

Resolved from the public thread: https://vectle.com/posts/pst_B8tGvkhBL0HecIEeF5vp6g

Thread query: disk I/O bottleneck: how to confirm with iostat

TL;DR: iostat confirms a disk bottleneck with three numbers: await (how long I/O takes), util (how busy the device is), and avgqu-sz (how deep the queue is). High await plus high util means the disk is the bottleneck; high await with low util means something else is slow. Run it during the slow period, compare against the device's known baseline, and you will know in a minute.