How to choose a VDS server: a sizing guide

Server plans are usually chosen by guesswork: "get the big one so we do not run out" or "get the cheapest and see". Both cost money — one pays for capacity you never use, the other for a migration you did not need yet.

The right method is measurement. If you already run a site, the data is in your hands.

Step 1: Measure what you use now

If you have a server or hosting account today, record these three values:

bashfree -h                    # memory usage
nproc && uptime            # core count and load average
df -h                      # disk usage

Load average shows how hard the server is working. Below your core count means you have headroom; consistently above it means the processor is the bottleneck.

For memory, read the available column of free -h; used is misleading because Linux uses free memory as cache.

Starting from scratch? Use the baselines below.

Step 2: A starting point by workload

• Corporate brochure site, a few hundred visitors a day: 2 GB RAM, 2 cores. Shared hosting often suffices; the reason to move to a VDS is usually control.
• WordPress, a few thousand visitors a day: 4 GB RAM, 2-4 cores. With caching configured properly this lasts a long time.
• WooCommerce / membership site: 8 GB RAM, 4 cores. Cart and account pages cannot be cached, so PHP load is permanent.
• API or backend service: Measure memory per request and multiply by concurrent requests. Do not estimate.
• Database server: The active working set should fit in memory. When it does not, reads hit disk and performance falls sharply.

Step 3: Which resource is your bottleneck?

You do not need to grow all three. The symptoms tell you which one is tight:

• Pages load slowly, load average high → processor
• Server freezes intermittently, swap usage rising → memory
• Database queries slow, disk wait high → disk
• Large files download slowly → network capacity

Growing the wrong resource spends money without fixing anything.

Step 4: Decide who will manage it

This question is overlooked more often than the specifications, and it shapes the outcome more.

With a VDS, root access means operating system maintenance transfers to you: security patches, firewall, backups, monitoring. If nobody on your team can take that on, you have three options:

1. Install a control panel (Plesk or cPanel) — it makes the job considerably easier
2. Buy a managed service
3. Stay on shared hosting

Buying a larger server does not remove the management need; it increases it.

Step 5: Leave room to grow, but not too much

About 40% above your current usage is a reasonable buffer. More than that is paying for capacity you do not use.

That is the advantage of a VDS: you can move up mid-term and have the remaining balance credited. So there is no reason to over-buy at the start.

Watch the terminology

The definitions of VDS and VPS vary between providers. Some guarantee resources, some oversell. Before ordering, ask plainly: "are the processor and memory in this plan allocated to me alone?" If the answer is not clear, they probably are not. We covered the difference in our VDS, VPS and dedicated comparison.

If you would like help sizing, send us your current usage figures.