The short answer
| Workload | RAM | Plan |
|---|---|---|
| Static site, small API, dev box | 2 GB | ₹699$7.94/mo |
| 1–3 WordPress sites, cached | 4 GB | ₹699$7.94/mo |
| Production WordPress + MySQL | 8 GB | ₹1,349$15.33/mo |
| WooCommerce store | 8–16 GB | ₹1,349$15.33–₹2,699$30.67/mo |
| 10–20 sites behind cPanel | 16 GB | ₹2,699$30.67/mo |
| Redis or Elasticsearch node | 16 GB+ | ₹2,699$30.67/mo |
| Tally on Cloud, 1–2 users | 8 GB | ₹1,499$17.03/mo |
| Modded Minecraft, 20–40 players | 16 GB | ₹2,699$30.67/mo |
| CI runners, build servers | 16–32 GB | ₹2,699$30.67–₹4,999$56.81/mo |
Prices exclude 18% GST. The rest of this explains where those numbers come from.
What actually uses the memory
On a typical LAMP or LEMP box:
- The OS — 200–400 MB for a minimal Ubuntu or AlmaLinux with no desktop.
- MySQL / MariaDB — 500 MB to 2 GB. The InnoDB buffer pool is the big one, and it should ideally hold your whole working data set.
- PHP-FPM — 40–120 MB per worker, and a WordPress site with a page builder sits at the top of that range. Ten workers at 100 MB is a gigabyte.
- The web server — Nginx is 50–100 MB, Apache with mod_php considerably more, LiteSpeed in between.
- Redis, if used — whatever you cap it at, typically 256 MB to 2 GB.
- cPanel, if installed — 1 GB before you host anything. Budget for it.
Add those up for your stack, then add 25–30% headroom. Memory that is full at idle has nothing left for your busiest hour.
Why running out is worse than being slow
A CPU-starved server is slow. A memory-starved server fails. Linux swaps to disk first — orders of magnitude slower — and when that is exhausted the out-of-memory killer picks the largest process and kills it. That is almost always MySQL, and the visible symptom is "Error establishing a database connection" until something restarts it.
This is why the honest advice is to size RAM generously and CPU tightly. CPU pressure degrades; RAM pressure breaks.
Rules of thumb that hold up
- WordPress, cached: ~1 GB per busy site, including its share of MySQL.
- WooCommerce: double it. Cart, checkout and account pages cannot be page-cached, so they hit PHP and MySQL on every request.
- Minecraft: ~1 GB per ten vanilla players, plus whatever the modpack asks for, rounded up.
- Tally on Cloud: Windows Server needs 4 GB before Tally starts; 8 GB covers one or two concurrent users comfortably.
- Node and Python APIs: measure. They vary more than anything else on this list.
Check what you are using now
# free memory, human readable
free -h
# the ten biggest processes by memory
ps aux --sort=-%mem | head -11
# is it swapping?
vmstat 1 5
In free -h, look at available, not free — Linux uses spare memory for disk cache and hands it back on demand, so a low "free" figure is normal and healthy. In vmstat, non-zero si/so columns mean active swapping, which means buy more memory.
Do not over-buy either
A 32 GB server running a 3 GB workload is money spent on nothing. Our plans resize in place — vCPU, RAM and disk grow with a single reboot, and nothing is reinstalled — so the right strategy is to start one size down and move up when the numbers say to.
If you tell us the workload on +91 75994 50220, we will size it with you. We would rather sell you the ₹699$7.94 plan that fits than the ₹2,699$30.67 one that does not.
The full ladder is on the KVM VPS page.