How much RAM and CPU your VPS really needs

It’s easy to overpay for a VPS or, worse, to choke a real workload. Here are honest starting points and how to know when to grow.

Sensible starting points

A static site or a small blog runs comfortably on 1–2 GB of RAM and one core. A busier CMS or a small online store wants 2–4 GB and two cores once caching and a database are involved. Databases and analytics are memory-hungry: start at 8 GB. AI/ML inference is the outlier — 16 GB and up, plus real CPU or a GPU.

RAM or CPU first?

For most web workloads, RAM is the limiting resource: run out of it and the server starts swapping to disk and crawls. CPU matters for compute-heavy work — video, compression, model inference — and for handling many simultaneous requests. When in doubt, add RAM before cores.

Leave headroom, then scale

Your plan is a ceiling, not a target. Aim to use roughly two-thirds of RAM at normal load so spikes don’t take you down. The good news: on most providers, such as RUVDS, you can start small and resize later, so there’s no need to over-buy on day one.

Watch the real numbers

Once live, watch memory use, load average and disk I/O for a week. If RAM sits near the ceiling or load is consistently high, size up one step. The calculator’s presets per task are a reasonable first guess — adjust from what you actually see.