Kyrnet opens soon. Get notified of the launch on our Discord.

Join our Discord →
KyrnetKyrnet
Getting started

How many vCPU, how much memory and storage for my VPS?

Practical guidelines to size your VPS for your project, and how to tell when it is time to add resources.

2 min read · Updated on

With a custom VPS, you pay for each vCPU, each GB of memory and each GB of storage. The right approach: start lean, monitor, then add resources when needed. Upgrades are done from the client area, and only the difference is billed, prorated over the time remaining.

Guidelines by project

These values are starting points, not rules: a busy or poorly optimized site will need more.

ProjectvCPUMemoryStorage
Brochure site, WordPress blog12 GB25 GB
Online store (WooCommerce, PrestaShop)24 GB50 GB
Discord bot, small API, internal tool11 to 2 GB25 GB
Minecraft server (about ten players)2 to 46 to 8 GB50 GB
Several sites or Docker containers48 GB100 GB
Medium-sized database48 to 16 GB100 GB or more

What each resource does

  • vCPU: computing power. It matters when many things run at once (web requests, builds, players).
  • Memory: usually the first thing to run out. When it is full, the server slows down sharply or stops programs.
  • Storage: the system (a few GB), your files, databases and logs. Keep at least 20% free.

Knowing when to upgrade

Connect over SSH and check:

free -h    # used and available memory
df -h      # disk space per partition
htop       # live processors and programs (apt install htop)

The statistics in your client area also show processor and memory usage over time. If memory stays above 85% or the processor above 80% all the time, it is time to add more.

Starting small costs nothing extra

The price follows your configuration exactly: going from 2 to 4 GB of memory only adds the price of 2 GB. No need to oversize "just in case".

Further reading