How to choose VPS specs: CPU, RAM and NVMe

Picking VPS specs feels like guesswork until you know what each number does. Here's how to size a server so you neither overpay nor run out of headroom.

RAM is usually the first wall you hit

Memory is where most projects run short. Every process — your web server, database, language runtime, control panel — holds RAM. Run out and Linux starts killing processes (the dreaded OOM killer) or thrashing swap, and everything crawls.

Rough starting points:

• 1 GB — a small static site, a single lightweight service, a bot.
• 2 GB — a WordPress site, a small Node.js app, a personal Nextcloud.
• 4 GB — several sites, a busier app plus its database, a control panel like cPanel or CyberPanel.
• 8 GB+ — heavy databases, many sites, containers, or memory-hungry apps.

Rule of thumb: pick the RAM you expect to need, then go one tier up if the price gap is small. It's the resource you'll miss most.

vCPU: cores for concurrency

vCPUs are virtual processor cores. More cores help you handle many requests at once and speed up parallel work like image processing or builds.

• 1 vCPU — fine for low-traffic sites and single apps.
• 2 vCPU — a comfortable default for most web apps and WordPress.
• 4+ vCPU — high traffic, background job queues, compilation, or CPU-heavy work.

Most web workloads are I/O-bound, not CPU-bound, so don't over-buy cores at the expense of RAM.

NVMe storage: size and speed

Storage has two dimensions. Capacity is obvious — count your OS (a few GB), your app, and your data with room to grow. Speed is the underrated one. NVMe drives are dramatically faster than the SATA SSDs older hosts still ship, which shows up directly in database query times and file operations.

Nxeon uses NVMe across the board, so even a small plan feels responsive. For sizing:

• 25–50 GB — most sites and apps.
• 80–160 GB — media libraries, larger databases, Nextcloud with real files.

Check your usage anytime with:

df -h        # disk space
free -h      # memory
nproc        # number of CPUs

Bandwidth

Bandwidth is monthly data transfer. A normal website uses far less than people fear — text and code are tiny. Heavy video, large downloads, or a busy media site are what actually consume it. Most generous VPS plans include more than a typical site will ever use.

Match specs to the job

• Static / brochure site: 1 vCPU, 1–2 GB RAM, 25 GB NVMe.
• WordPress: 2 vCPU, 2–4 GB RAM, 40 GB NVMe.
• Node.js / Next.js app + database: 2 vCPU, 4 GB RAM, 50 GB NVMe.
• Several sites or a control panel: 2–4 vCPU, 4–8 GB RAM, 80 GB NVMe.
• Self-hosted cloud (Nextcloud) with files: 2 vCPU, 4 GB RAM, 160 GB NVMe.

Start smaller — you can resize

The best strategy is to start at a sensible tier and watch the numbers. If free -h shows memory constantly near full, or your CPU sits pinned, it's time to move up. On Nxeon you can resize an existing VPS to add vCPU and RAM without rebuilding, so there's no penalty for starting lean.

Signs you've outgrown your current size

• Consistent high memory use and swap activity.
• Load average above your core count for long stretches (uptime).
• Slow database queries that profile as disk- or CPU-bound.

Size for today plus a little headroom, monitor the real numbers, and upgrade when the data tells you to — not before.