How to Choose RAM, CPU and Disk Size for Your VPS

Most VPS sizing decisions go wrong in the same direction: people overprovision because the next tier up "feels safer", then pay for resources that sit idle for years. The right size for a VPS is the smallest tier that handles your peak load with sensible headroom, plus a clear upgrade path when you grow. This guide walks through workload-based sizing for the four most common self-hosted scenarios (WordPress, Nextcloud, development, mail server) and maps them to specific MMITech tiers.

The General Principle

Three numbers matter:

1. RAM: should sit around 60 to 70 percent at typical load, leaving room for spikes and page cache
2. CPU: should idle most of the time, with brief bursts during peak operations
3. Disk: should have at least 30 percent free at all times, more if you do large operations like database dumps or media uploads

If any of these regularly cross 85 percent, you are at the wrong tier.

Our Tier Map

Both Cloud VPS and AMD VPS share the same shape:

Custom configurations are also available if none of the tiers fit cleanly.

WordPress

Tiny blog or personal site (< 5,000 visitors/month)

Recommendation: Cloud Micro (€4/month)

A WordPress site with light traffic and reasonable caching runs comfortably on 1 vCore and 1 GB of RAM. Use a caching plugin (WP Super Cache or LiteSpeed Cache) and a real opcode cache, and the site will outperform expectations.

Sizing notes:

• Disk: 20 GB is plenty for the application, theme, and a few hundred MB of media
• RAM: PHP-FPM with 5 to 10 workers fits in 1 GB if you keep plugins reasonable
• Bottleneck to watch: too many heavy plugins. Plugin count matters more than visitor count for RAM use.

Business site or small-traffic e-commerce (5,000 to 50,000 visitors/month)

Recommendation: Cloud Starter (€12/month)

2 vCores and 4 GB of RAM is the sweet spot for a real business site, including WooCommerce up to a few hundred orders per month. Add Redis or Memcached for object caching, configure 15 to 20 PHP-FPM workers, and you have meaningful headroom.

Sizing notes:

• Use a CDN (Cloudflare free tier works) for static assets to keep CPU usage on the VPS focused on PHP
• Database: MariaDB tuned with 1 GB buffer pool fits comfortably
• Bottleneck to watch: image-heavy pages without WebP/AVIF conversion

Medium-traffic WooCommerce or content site (50,000 to 200,000 visitors/month)

Recommendation: Cloud Basic (€24/month) or Cloud Advanced (€48/month)

At this scale, RAM is usually the first constraint. 8 GB lets you run PHP-FPM with 30 to 40 workers, MariaDB with a 2 GB buffer pool, Redis, and a reverse proxy without juggling. If you run live search (Elasticsearch, Meilisearch) or have large product catalogs, jump to Advanced for the additional headroom.

For WooCommerce specifically, Cloud VPS is the safer pick because order data must survive node failures.

Development Environment

Development VPS sizing depends entirely on what you build.

Single-developer, single-project (web, API, scripting)

Recommendation: AMD Starter (€12/month)

For a developer running one or two projects, Docker containers, a database, and a code editor over SSH, 2 vCores and 4 GB RAM are sufficient. AMD VPS makes sense here because compile times benefit from single-thread speed and local NVMe.

Multiple projects, frequent builds, CI runner

Recommendation: AMD Basic (€24/month)

4 vCores and 8 GB RAM handle parallel builds, multiple running services, and CI/CD pipelines. If your builds are Node.js or Go-heavy, you will see the AMD single-thread advantage clearly.

Team development with shared services

Recommendation: AMD Advanced (€48/month) or split between two VPS

For a team of three to five developers sharing a remote development environment, you usually want to separate the persistent services (database, queue, search) from the development sandbox. Two Starter-tier VPS often work better than one Advanced.

Mail Server

Mail servers are unique because they need almost no CPU and almost no disk, but they need enormous reliability and a clean IP reputation.

Personal or small business mail (< 20 users)

Recommendation: Cloud Starter (€12/month)

A Postfix + Dovecot + Rspamd + Postfwd stack with Roundcube webmail fits comfortably in 4 GB RAM. The 50 GB disk holds plenty of mail for years of normal use.

Sizing notes:

• Cloud VPS over AMD VPS: mail delivery should survive node failures
• IP reputation matters more than spec: a fresh IP needs warming
• Bottleneck to watch: spam filter (Rspamd or SpamAssassin) is the heaviest CPU consumer

Medium business mail (20 to 100 users)

Recommendation: Cloud Basic (€24/month)

4 vCores, 8 GB RAM handles 100 users with good spam filtering, calendar (SOGo or DAViCal), and mobile sync (ActiveSync via z-push or similar). Disk grows linearly with users; if you keep mail attachments, plan for 1 to 5 GB per user.

Quick Reference Matrix

How to Validate Your Sizing After Deployment

Within the first week of running production, check:

# RAM
free -h
# CPU and steal time
vmstat 1 10
# Disk usage and IO
df -h
iostat -x 1 5
# Active connections
ss -s

If RAM stays under 70 percent during peak, CPU has visible idle time, and disk has 40+ percent free, you are at the right tier or could even step down. If RAM is over 80 percent or you see swap activity, step up at the next billing cycle.

Upgrade Path

Upgrading between tiers on our platform is straightforward: schedule a brief maintenance window, and resources are reallocated within minutes thanks to the Ceph backend on Cloud VPS. For AMD VPS, resources scale similarly within a node's available capacity.

If you outgrow Advanced, the conversation shifts to either a custom VPS configuration or a dedicated server. Our team will look at your real metrics and recommend the right next step.

FAQ

Should I overprovision "just in case"? No. Pick the tier matching your real workload, and use the upgrade path if needed. The Ceph backend on Cloud VPS makes resource upgrades fast and low-disruption.

What if my workload is bursty? For predictable bursts (a daily sync, a monthly batch), you can stay on a smaller tier and let the burst run a bit slower. For random unpredictable bursts (viral content, marketing campaigns), size for the burst, not the average.

How much disk should I leave free? At least 30 percent at all times. Database operations, OS updates, and backup operations all need temporary disk space. Running a disk below 10 percent free starts to affect performance and reliability.

Is RAM or CPU more often the bottleneck? For web and self-hosted application workloads, RAM almost always saturates first. CPU spikes are usually brief; sustained RAM pressure is what forces the upgrade.

Can I downgrade if I overprovisioned? Yes, with a brief maintenance window. Many customers downgrade after realizing their initial estimate was too generous.

Pick Your Starting Point

Match your workload to one of the scenarios above, pick the tier we recommend, and start there. If you guessed wrong by one tier in either direction, upgrades and downgrades take minutes on our Cloud VPS and AMD VPS platforms, so the cost of an imperfect first guess is small.