Cheap Virtual Server Hosting: How to Read the Spec Sheet Without Being Fooled

A cheap virtual server host can advertise “8 vCPU” and still deliver less compute than a competitor’s “2 vCPU” plan on the same crawl budget. The gap comes from the words around the number: what vCPU type is being sold, how many tenants share the physical core, whether the credits are burstable, and what IOPS ceiling the disk enforces under load. The spec sheet is a contract if you read it closely and a marketing brochure if you skim it.

Three lines decide most purchases: core count, RAM, and disk type. Everything else — the port speed, the “unmetered” clause, the snapshot count — is a modifier. Learn to price the first three per dollar and the rest is mostly risk management. The point of a cheap virtual server hosting plan is to get more usable silicon per dollar, not a longer feature list.

vCPU count is not core count

A vCPU is a time slice of a physical core, or of a hyperthread. When a host says “4 vCPU” you have four schedulable queues, not four cores. On a modern Xeon or EPYC with hyperthreading, two vCPUs may map to two threads on one core, which means a single floating-point-heavy process gets roughly one core’s throughput. For web serving that is fine. For compiling, encoding or running a game server, it is not.

Ask a direct question: are the vCPUs threaded or full cores, and what is the physical CPU family? A 2 vCPU plan on dedicated cores frequently outperforms a 4 vCPU plan on shared threads for single-threaded PHP. Benchmark what you care about with one process, not with four parallel ones, because parallel benchmarking hides scheduling contention behind throughput numbers you will never see in production.

Fair-share, dedicated and the oversubscription ratio

Most $5–$15 plans are fair-share: you get a guaranteed floor and a burst ceiling, and the host sells capacity on the assumption that every tenant is idle most of the day. Fair-share is fine when the ratio is stated and reasonable. It becomes a lottery when the host packs 16 tenants onto a core and calls it “dedicated-class performance.”

Numbers to look for: a 1:1 to 1:4 vCPU oversubscription ratio is genuinely dedicated-ish; 1:8 is normal shared hosting; beyond that you are buying the right to queue. RAM oversubscription matters more than CPU for databases, because a host that swaps your neighbours’ pages to disk to fit another tenant will make your query latency spiky in ways your own monitoring never explains.

Burstable credits expire, and they expire quietly

Credit-based plans give you a baseline percentage of a core plus a bucket of credits you spend when you exceed it. A typical arrangement is 20% baseline with 200 credits, where one credit equals one minute of full-core use. Sustained heavy load drains the bucket, and when it empties you are throttled to 20% of a core — which on a busy site looks exactly like a network outage.

Calculate the steady-state ceiling before you buy: baseline percentage times core count. A 2 vCPU plan at 20% baseline gives you 0.4 cores of sustained throughput. If your workload needs 1.5 cores continuously, you will burn through any credit allowance in hours and live throttled for the rest of the month. Unlimited burst is a marketing term; every host enforces a sustained limit.

Spec-sheet phrase	What it usually means	Threshold to accept
“4 vCPU”	4 threads, possibly on 2 cores	Ask threaded vs full core
“Dedicated resources”	Unknown until ratio is stated	1:1 to 1:4 in writing
“Burstable to 100%”	Credit bucket with a baseline	Baseline ≥ 25% for production
“High IOPS SSD”	Shared array, cap unstated	≥ 3,000 random 4K IOPS
“Unmetered bandwidth”	Port cap plus fair-use clause	Port ≥ 200 Mbps, clause in writing

IOPS caps turn fast disks into slow disks

NVMe with a 500 IOPS cap is a marketing line, not a storage tier. A small MySQL instance doing 300 writes per second needs roughly 600–900 random IOPS once journal, doublewrite and index updates are counted. If the plan caps you at 500 total, the database will stall at peak and your slow query log will blame the application.

Ask for the burst IOPS figure and the sustained figure separately. A plan that offers 20,000 burst IOPS and 1,000 sustained is workable for a blog with traffic spikes. A plan with only a burst number and no sustained guarantee is sold on the assumption you will never measure it. Disk throughput caps measured in MB/s are a second throttle, and 50 MB/s will bottleneck a backup restore even if IOPS look healthy.

“Unmetered” bandwidth has a port and a clause

Unmetered rarely means unlimited. It usually means no fixed monthly quota, subject to a fair-use clause and a port speed cap. A 100 Mbps port delivers about 32 TB per month if saturated around the clock, which is plenty for most sites — but the plan that throttles you after 2 TB “to protect network quality” is metered with extra steps.

Read the fair-use clause for three phrases: throttling thresholds, whether static file serving counts, and whether abuse reports from your visitors can suspend the plan. A host that treats a traffic spike as a violation is not suitable for anything that might trend. Cheaper plans also route traffic through a shared uplink, so peak-hour throughput can be half the advertised port speed.

The lines worth more than another vCPU

• Backup inclusion. A $2 snapshot add-on over 12 months is $24 — often the same as the step from $10 to $12 a month.
• IPv4 count. A second IPv4 for a mail server or VPN endpoint can be $1–$3 per month, or free; ask before assuming.
• Setup fee. A $15 one-time fee on a $5 plan raises the first-year cost by 25%.
• Renewal price. A $6 intro rate renewing at $12 is a $12 plan with a coupon on the front.
• Snapshot restore time. Free backups that take four hours to restore are a liability during an incident.

A five-minute read of any spec sheet

Circle the vCPU type, the RAM, the disk type and the transfer allowance. Underline the words dedicated, unmetered and burstable, then demand a number next to each. Divide the monthly price by RAM in gigabytes; anything above $6 per GB at the 2 GB tier is expensive for this market, and anything under $4 is worth a second look at the IOPS cap.

Finally, check the exit terms. A plan that refunds only within seven days and renews at 1.8x is more expensive than a plan at $2 more per month with pro-rated refunds and price-locked renewal. Comparing budget virtual server plans by these five numbers, in that order, filters out most of the noise before you ever run a benchmark.