{"id":1709,"date":"2026-11-13T22:41:26","date_gmt":"2026-11-13T22:41:26","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=1709"},"modified":"2026-11-13T22:41:26","modified_gmt":"2026-11-13T22:41:26","slug":"cpu-steal-vs-iowait-vps-slowdown-triage","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/","title":{"rendered":"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Every slowdown triage on a VPS eventually forks into the same question: is the box waiting on the disk, or is it running and simply not getting CPU from the hypervisor? Both show up as &#8220;the site is slow&#8221; and both raise load average, but they have opposite remedies \u2014 one wants a query fix or a storage upgrade, the other is a provider conversation. <code>top<\/code> showing <code>%wa<\/code> and <code>%st<\/code> is not enough to decide, because those columns are fractions of a sampling window and hide whether the blocked time is on the application&#8217;s behalf or the host&#8217;s.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The method below takes about ninety seconds on a live incident and produces a defensible answer: steal share, blocked-task share, per-device service time, and whether I\/O the instance issued is actually completing at the rate the provider promised. If you have already established the baseline for your instance&#8217;s storage tier \u2014 see the <a href=\"https:\/\/virtualserversvps.com\/\" target=\"_blank\" rel=\"noopener\">VPS disk latency tier verification<\/a> procedure \u2014 the comparison is direct.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: one vmstat sample tells you which side to pursue<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run <code>vmstat 1 10<\/code> during the incident and read the two right-hand columns of blocks that matter: <code>wa<\/code> (CPU waiting on I\/O) and <code>st<\/code> (time stolen by the hypervisor). The first row is an average since boot and must be discarded. Use the per-second rows.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>vmstat 1 10 | tee \/tmp\/vm.txt\n# columns:  r  b   swpd   free   buff  cache   si   so  bi  bo   in   cs us sy id wa st\n# decision rule (per-second rows, averaged by eye or awk):\n#   st &gt; 3  AND  wa  hypervisor CPU contention\n#   wa &gt; 15 AND  st  genuine I\/O wait\n#   both high                  -&gt; storage backend under pressure (shared LUN)<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: separate steal from real CPU shortage<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Steal time is the hypervisor&#8217;s own accounting of time your vCPU was runnable but the physical CPU was busy with another guest. It is reported per vCPU in <code>\/proc\/stat<\/code> and aggregated by <code>mpstat<\/code>. A sustained 5\u20138% on a 2 vCPU instance is roughly a tenth of one core \u2014 noticeable, occasionally acceptable. Above 15% on a production instance is a host problem.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># per-vCPU breakdown, 1s intervals\nmpstat -P ALL 1 10\n\n# raw steal ticks over a 60s window, converted to percent\nawk '\/^cpu[0-9]\/{print $1}' \/proc\/stat\na=$(awk '\/^cpu \/{print $9}' \/proc\/stat); ad=$(awk '\/^cpu \/{print $1}' \/proc\/stat)\nsleep 60\nb=$(awk '\/^cpu \/{print $9}' \/proc\/stat); bd=$(awk '\/^cpu \/{print $1}' \/proc\/stat)\necho \"steal% = $(echo \"scale=2; 100*($b-$a)\/($bd-$ad)\" | bc)\"<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: attribute I\/O wait to a device and a process<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If <code>wa<\/code> is high, the next question is whether the device is busy or merely slow. <code>%util<\/code> near 100 with rising <code>await<\/code> is saturation; <code>%util<\/code> at 30 with 40 ms <code>await<\/code> is a slow backend \u2014 often a shared LUN, or your burst credit exhausted and IOPS throttled at the hypervisor layer.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>iostat -dxm 1 5 \/dev\/vda | tail -20\n# r\/s w\/s rMB\/s wMB\/s await r_await w_await aqu-sz %util\n\n# who is issuing it\nsudo pidstat -d 1 5\n# or the slower but always-available route\nfor p in \/proc\/[0-9]*; do\n  echo \"$(basename $p) $(awk '{s+=$6} END{print s}' $p\/io 2&gt;\/dev\/null)\"\ndone | sort -k2 -n | tail -10<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Watch <code>aqu-sz<\/code> vs the queue depth the device reports. On a virtio disk, <code>cat \/sys\/block\/vda\/queue\/nr_requests<\/code> is the guest-side cap (often 128), but the hypervisor may only have 32 slots available for your instance. If <code>aqu-sz<\/code> exceeds roughly 25% of the reported depth while <code>await<\/code> rises linearly, you are being queued downstream and the extra in-flight requests are pure latency.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: test the floor with a controlled write<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One minute of fio at a fixed queue depth separates &#8220;my workload is heavy&#8221; from &#8220;this volume cannot do what was sold&#8221;. Run it to a temp file, not the device, and compare against your recorded baseline.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo fio --name=floor --filename=\/tmp\/floor.bin --size=1G --bs=4k \\\n  --rw=randwrite --iodepth=16 --numjobs=1 --runtime=30 --time_based \\\n  --ioengine=libaio --direct=1 --group_reporting\n\n# drain caches first so you measure the device, not page cache\nsudo sync; echo 3 | sudo tee \/proc\/sys\/vm\/drop_caches<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Read the <code>clat<\/code> percentiles, not the mean. A p99 of 12 ms with a mean of 2 ms on a 4 KiB direct write indicates the tail is being throttled, which is exactly what an IOPS credit system looks like: most requests sail through, one in a hundred queues behind the throttle window.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: check memory pressure \u2014 the confounder<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Both symptoms have a third cause that mimics them: reclaim. When page cache is evicted aggressively, application reads become device reads, which shows as I\/O wait; and when kswapd runs hot, runnable work looks like steal because the scheduler is busy in kernel memory paths. Before blaming the host, confirm memory is not the driver.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cat \/proc\/pressure\/memory \/proc\/pressure\/io\nvmstat 1 3 | awk 'NR&gt;2{print \"si=\"$7\" so=\"$8\" free=\"$4\" cache=\"$6}'\ncat \/proc\/vmstat | grep -E \"pgscan|pgsteal|allocstall\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Rising <code>pgscan_direct<\/code> with nonzero <code>allocstall<\/code> is direct reclaim stalling allocations, and that is a memory sizing issue. Fixing it \u2014 a smaller buffer pool, a tighter PHP-FPM pool, or more RAM \u2014 frequently removes both the &#8220;I\/O wait&#8221; and the &#8220;steal&#8221; without any network or provider involvement.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A worked example: two incidents that looked identical<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Incident A: 4 vCPU instance, load 6.1, response times tripled. vmstat showed <code>us 22 sy 6 id 51 wa 4 st 17<\/code>. PSI CPU <code>some avg10<\/code> was 34. fio at queue depth 16 returned a healthy 0.9 ms p50, proving storage was fine. Conclusion: hypervisor CPU contention; the fix was a host migration or a dedicated-core plan, and no amount of application tuning helped.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Make the triage repeatable<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Collect <code>vmstat<\/code>, <code>mpstat -P ALL<\/code>, <code>iostat -dxm<\/code> and all three PSI files every minute into a single log, and keep a week. Ninety percent of triage arguments disappear when you can show a chart of <code>st<\/code> and <code>await<\/code> over the period a user complained about. The command that usually earns its keep is the simplest: <code>vmstat 1 60<\/code> piped to a file at the moment the alert fires, because both steal and I\/O contention are bursty and a five-minute monitoring average will hide the very window you care about.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When the data points at contention rather than configuration, the decision becomes commercial: keep a shared instance with unpredictable neighbours, or move to a <a href=\"https:\/\/virtualserversvps.com\/\" target=\"_blank\" rel=\"noopener\">VPS tier with guaranteed CPU and dedicated NVMe<\/a>. Either way, decide with counters in hand.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every slowdown triage on a VPS eventually forks into the same question: is the box waiting on the disk, or is it running and simply not getting CPU from the&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":2,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1709","post","type-post","status-publish","format-standard","hentry","category-performance-optimization"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage - Virtual Servers VPS Blog<\/title>\n<meta name=\"description\" content=\"Every slowdown triage on a VPS eventually forks into the same question: is the box waiting on the disk, or is it running and simply not getting CPU from\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage\" \/>\n<meta property=\"og:description\" content=\"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage\" \/>\n<meta property=\"og:url\" content=\"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/\" \/>\n<meta property=\"og:site_name\" content=\"Virtual Servers VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-13T22:41:26+00:00\" \/>\n<meta name=\"author\" content=\"Virtual-Servers-Vps-Editor\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Virtual-Servers-Vps-Editor\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/\",\"url\":\"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/\",\"name\":\"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage - Virtual Servers VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#website\"},\"datePublished\":\"2026-11-13T22:41:26+00:00\",\"author\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0\"},\"description\":\"Every slowdown triage on a VPS eventually forks into the same question: is the box waiting on the disk, or is it running and simply not getting CPU from\",\"breadcrumb\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/virtualserversvps.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#website\",\"url\":\"https:\/\/virtualserversvps.com\/blog\/\",\"name\":\"Virtual Servers VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/virtualserversvps.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0\",\"name\":\"Virtual-Servers-Vps-Editor\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g\",\"caption\":\"Virtual-Servers-Vps-Editor\"},\"sameAs\":[\"https:\/\/virtualserversvps.com\/blog\"],\"url\":\"https:\/\/virtualserversvps.com\/blog\/author\/virtualserversvps\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage - Virtual Servers VPS Blog","description":"Every slowdown triage on a VPS eventually forks into the same question: is the box waiting on the disk, or is it running and simply not getting CPU from","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/","og_locale":"en_US","og_type":"article","og_title":"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage","og_description":"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage","og_url":"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/","og_site_name":"Virtual Servers VPS Blog","article_published_time":"2026-11-13T22:41:26+00:00","author":"Virtual-Servers-Vps-Editor","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Virtual-Servers-Vps-Editor","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/","url":"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/","name":"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage - Virtual Servers VPS Blog","isPartOf":{"@id":"https:\/\/virtualserversvps.com\/blog\/#website"},"datePublished":"2026-11-13T22:41:26+00:00","author":{"@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0"},"description":"Every slowdown triage on a VPS eventually forks into the same question: is the box waiting on the disk, or is it running and simply not getting CPU from","breadcrumb":{"@id":"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vs-iowait-vps-slowdown-triage\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/virtualserversvps.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Is It CPU Steal or I\/O Wait? A 90-Second VPS Slowdown Triage"}]},{"@type":"WebSite","@id":"https:\/\/virtualserversvps.com\/blog\/#website","url":"https:\/\/virtualserversvps.com\/blog\/","name":"Virtual Servers VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/virtualserversvps.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0","name":"Virtual-Servers-Vps-Editor","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g","caption":"Virtual-Servers-Vps-Editor"},"sameAs":["https:\/\/virtualserversvps.com\/blog"],"url":"https:\/\/virtualserversvps.com\/blog\/author\/virtualserversvps\/"}]}},"_links":{"self":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/1709","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/comments?post=1709"}],"version-history":[{"count":1,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/1709\/revisions"}],"predecessor-version":[{"id":1710,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/1709\/revisions\/1710"}],"wp:attachment":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/media?parent=1709"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/categories?post=1709"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/tags?post=1709"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}