{"id":1655,"date":"2026-11-05T04:25:14","date_gmt":"2026-11-05T04:25:14","guid":{"rendered":"https:\/\/affordablevpsserver.com\/blog\/?p=1655"},"modified":"2026-11-05T04:25:14","modified_gmt":"2026-11-05T04:25:14","slug":"disk-latency-test-oversold-vps","status":"publish","type":"post","link":"https:\/\/affordablevpsserver.com\/blog\/disk-latency-test-oversold-vps\/","title":{"rendered":"Detecting Oversold Disk Performance on a Budget VPS"},"content":{"rendered":"

TL;DR \/ Summary:<\/strong> A cheap VPS can look fine on paper and still deliver a fraction of its advertised disk speed because the host oversold the array. Steady-state latency and write jitter expose it in ten minutes, long before your database does.<\/p>\n

What “oversold” actually means on a VPS<\/h2>\n

Virtualisation lets a host sell the same physical cores and spindles several times over. CPU oversubscription is usually tolerable because most tenants idle. Disk oversubscription is not, because storage latency is cumulative: every tenant’s write queue joins the same device queue.<\/p>\n

The symptoms are familiar. A WordPress admin takes nine seconds to load a page, a database import crawls, and top<\/code> shows almost no CPU usage. Nothing is broken, which is why support tickets go nowhere.<\/p>\n

You cannot see the neighbour’s usage directly. What you can measure is the effect: latency that spikes under load you did not create.<\/p>\n

Three measurements worth running<\/h2>\n

Start with sequential write throughput, then random read latency, then a sustained hold to see whether the numbers collapse after the initial burst.<\/p>\n

The burst is the trick to watch for. Many hosts buffer writes in RAM or on a fast tier, so the first few gigabytes look excellent. Once the cache fills, a budget node drops to a fraction of the earlier figure. A thirty-second test will never see that; a two-minute test usually will.<\/p>\n

A quick diagnostic sequence<\/h3>\n