⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Linux & SRE Interview Questions Scenario 1 of 135 in Linux & SRE
Senior DevOps / SRE Linux Performance & SRE Core SRE Methodology
🎯 Target Role / Context: Linux Systems Performance & SRE

Q: Production server becomes slow — how do you identify CPU/memory/disk/network issues?

Mastering the USE Method (Utilization, Saturation, Errors) to isolate system bottlenecks across CPU, Memory, Disk I/O, and Network in under 60 seconds.

#Linux #USE Method #vmstat #iostat #sar #Troubleshooting
🎙️ Candidate Opening & Architectural Context
"When a production server becomes slow, I apply Brendan Gregg's USE Method (Utilization, Saturation, Errors) using a systematic 60-second command checklist to isolate which subsystem is bottlenecking."
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: When a production server becomes slow, I apply Brendan Gregg's USE Method (Utilization, Saturation, Errors) using a systematic 60-second command checklist to isolate which subsystem is bottlenecking.

1️⃣

First 15 Seconds: System Overview

Assess overall system pressure:

  • uptime: Look at load average (1m, 5m, 15m). Compare against core count (nproc). If 4 cores and load average is 28, system is heavily saturated.
  • dmesg -T | tail -30: Check kernel ring buffer for hardware errors, TCP drop warnings, or OOM killer events. Compare with our Pod CrashLoopBackOff & OOMKilled exit code 137 runbook.
2️⃣

CPU vs Disk I/O: vmstat 1 5

The most informative single command in Linux:

  • Run: vmstat 1 5 and read the columns:
  • r (run queue): Processes waiting for CPU. If r > total cores, CPU is saturated.
  • b (blocked): Processes blocked waiting for I/O. If b > 0, system is waiting on disk/NFS.
  • us (user) vs sy (system): High us = application code. High sy = kernel context switching or excessive syscalls.
  • wa (iowait): High wa (>20%) = CPU is idle because it is waiting for disk/storage to respond! The bottleneck is DISK, not CPU!
Advertisement
3️⃣

Memory Check: free -h & vmstat swap

Inspect real available memory and paging:

  • free -h: Look at available (not free). Available accounts for reclaimable page cache and buffers.
  • In vmstat 1 5, look at si (swap in) and so (swap out). If so > 0, the system is actively thrashing memory to disk, causing severe latency.
  • dmesg -T | grep -i 'killed process': Check if kernel OOM killer has executed. For containerized workloads under memory pressure, see our Kubernetes Pod Pending & Memory Pressure runbook.
4️⃣

Disk I/O & Network Deep Dive

Isolate storage or packet bottlenecks:

  • Disk I/O (iostat -xz 1 5): Check %util and await. If %util > 90% or await > 15ms, physical EBS/disk storage is saturated.
  • Network (sar -n DEV 1 5): Check rxpck/s, txpck/s, and rxdrop/txdrop for dropped packets.
  • Socket Pressure (ss -s): Check TCP socket counts. If timewait or estab is in tens of thousands, connection pool exhaustion is occurring. For multi-tier cloud routing issues, cross-reference our Outside-In VPC Network Tracing runbook.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Use the USE Method. Run 'uptime' -> 'vmstat 1 5' -> 'free -h' -> 'iostat -xz 1 5'. High 'wa' in vmstat means Disk I/O bottleneck; high 'si/so' means memory swapping; high 'r' means CPU saturation."
⚡ 60-Second Elevator Pitch Talking Points
  • Step 1: 'uptime' -> compare 1/5/15m load average against 'nproc' core count.
  • Step 2: 'vmstat 1 5' -> check 'r' (CPU saturation), 'b' (I/O blocked), and 'wa' (if iowait is high, bottleneck is disk, not CPU).
  • Step 3: 'free -h' -> check 'available' memory; check 'si/so' in vmstat for swap thrashing.
  • Step 4: 'iostat -xz 1 5' -> check '%util' and 'await' response times for storage bottlenecks.
  • Step 5: 'sar -n DEV 1 5' and 'ss -s' -> check network throughput, dropped packets, and socket saturation.
  • Step 6: 'dmesg -T | tail -30' for OOM kills and hardware errors.
🎬 60-Second Video Walkthrough
Watch the Animated Breakdown & Practice Live

Mastered this procedure? Subscribe to @naveedkumbhar01 on YouTube for daily 60-second SRE incident runbooks, Kubernetes triage shortcuts, and high-impact interview elevator pitches.

🔔 Subscribe on YouTube (Free) ▶ Watch Short (60s) ↗
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Mistaking high Linux load average caused by uninterruptible I/O wait for compute CPU saturation Load average includes processes in uninterruptible disk sleep (D state); high load with low CPU indicates disk I/O bottlenecks or NFS hangs rather than compute saturation.
  2. Failing to check kernel ring buffer logs (dmesg -T) and journalctl during unexpected service crashes when addressing identify Systemd service exits and kernel OOM reaper events are logged directly to the kernel ring buffer and systemd journal rather than application log files.
  3. Diagnosing infrastructure outages unsystematically without adhering to the USE or RED methodologies Senior Linux engineers systematically evaluate Utilization, Saturation, and Errors across compute, memory, and disk rather than making random configuration changes.
  4. Applying kernel runtime sysctl parameters on the fly without persisting them to /etc/sysctl.d/ Applying runtime sysctl adjustments via sysctl -w without configuration persistence causes critical tuning to vanish upon server reboot.
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →