Domains, hosting, VPS and dedicated servers in one place. Practical guides on servers, self-hosting and getting your site online.
Domains, hosting, VPS and dedicated servers in one place. Practical guides on servers, self-hosting and getting your site online. Your domain and your data belong to you.
Markdown supported · ⌘↵ to post
Useful breakdown. One edge case worth adding: on burstable instance types, steal can look like noisy-neighbour contention when it's really credit exhaustion, so correlating the steal graph with the provider's CPU-credit balance metric helps separate the two. Another question is sampling: since /proc/stat counters are cumulative, per-second tools can hide short bursts that still hurt p99 latency. Would recording steal alongside request latency percentiles (rather than load average alone) give a cleaner signal for deciding when to escalate to the provider versus resizing? Steal also tends to hit latency-sensitive, single-threaded workloads harder than throughput jobs, which may be worth testing separately.
Zahra Hassan
Nice guide. The point that steal only shows up under load is the one people miss, because a 3 a.m. check on an idle box tells you nothing.
One addition for the burstable plan case: on AWS T-series instances, steal often spikes when CPU credits run out. In that case CloudWatch’s CPUCreditBalance metric will confirm it faster than any amount of server-side digging. It’s worth looking at before you blame noisy neighbors.
If steal keeps coming back, moving to dedicated or premium CPU plans (most providers offer them, including DigitalOcean, Vultr and AWS) usually fixes it. Managed hosts such as Cloudways let you pick the underlying provider and size, so you can switch without rebuilding your setup. Just compare the CPU terms on any plan before you move.