{"id":888,"date":"2026-08-14T23:15:27","date_gmt":"2026-08-14T23:15:27","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=888"},"modified":"2026-08-19T22:12:35","modified_gmt":"2026-08-19T22:12:35","slug":"cpu-steal-vps-performance","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/cpu-steal-vps-performance\/","title":{"rendered":"High CPU Steal on Your VPS? Measure It and Fix the Root Cause"},"content":{"rendered":"\n

CPU steal is the percentage of time your virtual machine wanted to run but the hypervisor gave the physical CPU core to another tenant. On shared VPS infrastructure it is the most common cause of “the server feels slow but nothing is using the CPU” complaints. Unlike memory pressure or a misconfigured application, steal is invisible in htop<\/code> unless you know which column to read, and it cannot be fixed with more RAM or a faster framework. This guide explains how to measure steal reliably, what the numbers mean, and what actually reduces it.<\/p>\n\n\n\n

How CPU steal shows up in your metrics<\/h2>\n\n\n\n

On Linux, the kernel accounts steal time in the st<\/code> column of top<\/code>, vmstat<\/code>, and mpstat<\/code>. It appears whenever the hypervisor schedules a different virtual machine on the physical core your vCPU depends on. The telltale signature is high st<\/code> with low us<\/code> and sy<\/code>: the CPU is not busy doing your work \u2014 it simply was not given time to do it.<\/p>\n\n\n\n

Tool<\/th>Command<\/th>What to look at<\/th><\/tr><\/thead>
top \/ htop<\/td>top -d 2<\/code><\/td>st<\/code> column; sustained >5% while load is high<\/td><\/tr>
vmstat<\/td>vmstat 1<\/code><\/td>st<\/code> column in the CPU section<\/td><\/tr>
mpstat<\/td>mpstat -P ALL 1<\/code><\/td>%steal<\/code> per vCPU<\/td><\/tr>
sar<\/td>sar -u 1 10<\/code><\/td>%steal<\/code> history via sysstat<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

What the numbers actually mean<\/h2>\n\n\n\n