How much CPU and RAM does my VPS need?

By the serverserv team · 6 min read · Updated 15 October 2026

Picking a VPS size is easier than it looks. Start from what you plan to run, choose the smallest plan that fits it with some headroom, and upgrade when your own measurements say so. This guide explains what each resource does and maps common workloads to the serverserv Linux KVM plans.

What each resource does

• vCPU is processing power. It matters for work that computes: building code, compressing images, encoding video, busy PHP or Python apps and game server logic. More vCPUs help when many things happen at the same time.
• RAM holds the programs that are running and the data they are working on. Databases use spare RAM to cache data, which makes them faster. When RAM runs out, the system starts swapping to disk or stops processes, and everything slows down.
• NVMe storage holds your operating system, applications, databases, files and logs. Leave space for backups, updates and growth.
• Bandwidth is the amount of data your server can send and receive each month. Most websites and apps use far less than the plan allowance; large downloads and video use the most.

For most small and medium projects, RAM runs out before CPU does, so RAM is often the best guide to which plan you need.

Start from your workload

Write down everything that will run on the server: the web server, the app, the database, background jobs, Docker containers and any control panel. Each one needs its own share of memory. A minimal Linux system uses only a few hundred megabytes, but a database, a control panel or a set of containers can each take far more.

Then think about traffic: how many visitors or users will be active at the same time, not how many visit in a month. A site with steady, modest traffic needs much less than one that gets sudden spikes.

If software you plan to use publishes minimum requirements, such as a control panel or a game server, treat those as the floor and add headroom on top.

Common workloads and the plans that fit

• Learning Linux, a personal VPN, a small bot or a simple static site: KVM Mini (1 vCPU, 2 GB RAM, 25 GB NVMe) is enough to start.
• One or two small WordPress or PHP sites, a small API or a lightweight app: KVM 1 (1 vCPU, 4 GB RAM, 50 GB NVMe) gives the database room to breathe.
• A production web app with its database, a Docker Compose stack of a few services, or a small game server for friends: KVM 2 (2 vCPU, 8 GB RAM, 100 GB NVMe). This is a good default for most real projects.
• Busier sites and stores, several apps on one server, larger databases or modded game servers: KVM 3 (4 vCPU, 16 GB RAM, 200 GB NVMe).
• Many containers, heavy databases, build runners or many client projects: KVM 4 (8 vCPU, 32 GB RAM, 400 GB NVMe).
• Large production workloads that need a lot of parallel processing and memory: KVM 5 (16 vCPU, 64 GB RAM, 800 GB NVMe).

These are starting points, not hard rules. The same app can need very different resources depending on how it is built and how it is used.

The Linux KVM plans at a glance

Every plan includes full root access and NVMe storage. Prices are per month.

• KVM Mini: 1 vCPU, 2 GB RAM, 25 GB NVMe, 2 TB bandwidth. From $6.29/mo on a 3 year term, or $8.99 monthly.
• KVM 1: 1 vCPU, 4 GB RAM, 50 GB NVMe, 4 TB bandwidth. From $10.49/mo on a 3 year term, or $14.99 monthly.
• KVM 2: 2 vCPU, 8 GB RAM, 100 GB NVMe, 8 TB bandwidth. From $16.49/mo on a 3 year term, or $23.99 monthly.
• KVM 3: 4 vCPU, 16 GB RAM, 200 GB NVMe, 15 TB bandwidth. From $27.99/mo on a 3 year term, or $39.99 monthly.
• KVM 4: 8 vCPU, 32 GB RAM, 400 GB NVMe, 40 TB bandwidth. From $48.99/mo on a 3 year term, or $69.99 monthly.
• KVM 5: 16 vCPU, 64 GB RAM, 800 GB NVMe, 60 TB bandwidth. From $90.99/mo on a 3 year term, or $129.99 monthly.

Need Windows instead? Windows RDP plans start at 1 vCPU and 4 GB RAM, because Windows Server needs more memory than a minimal Linux system. Want the server managed for you? See Managed VPS.

How to tell if your VPS is too small

Linux includes simple tools to check this. Run them at a busy time of day:

• free -h shows memory. Look at the "available" column. If it stays very low and swap use keeps growing, you need more RAM.
• top or htop shows which processes use the most CPU and memory.
• uptime shows the load average. If it stays above your number of vCPUs for long periods, work is queuing for the CPU.
• df -h shows disk space. Try to keep at least 15 to 20 percent free.

Before you upgrade, check for easy wins: add caching to your website, remove services you do not use, and tune your database settings to match your RAM. Sometimes one misbehaving process is the real problem.

Upgrading and planning ahead

You do not need to buy for the next five years. Start with a plan that fits what you run now, plus some headroom, and request an upgrade from your client area when you need it. Any price difference for the rest of your current billing period is invoiced when you upgrade.

Keep in mind that a 1, 2 or 3 year term gives a lower monthly price for the whole term. If you are confident about your size, a longer term saves money; if you are still testing, monthly billing keeps you flexible. Compare terms on the pricing page.

Questions