Skip to content

High-Performance Cloud Server: CPU, RAM and NVMe

High-Performance Cloud Server: CPU, RAM and NVMe
Blog 2 min read

How to size a cloud server: PHP workers and memory, database buffer, NVMe I/O and the measurements that show whether to scale up.

Size a cloud server from measurements. Memory runs out first on most web workloads, disk latency decides how fast a database feels, and CPU matters when requests do real computation. A guess that is twice too big costs money every month, and a guess that is half too small costs sleep.

RAM: the first limit you hit

  • PHP-FPM. Each worker holds memory, often tens of megabytes. Multiply the average by the number of workers you allow, then add the database and the system.
  • MySQL or MariaDB. Give the InnoDB buffer pool a large share when the database lives on the same machine, but leave room for the operating system.
  • Cache. Redis or Memcached on the same host eats RAM as well.
  • Swap. Use it as a safety net, not as capacity. A server that swaps under load is already too small.

CPU: cores versus clock

A single slow request uses one core. Many parallel requests need many cores. For a CMS, a few fast vCPUs usually beat many slow ones. For queue workers, image processing or builds, more vCPUs help. Watch the load average against the core count.

NVMe: why it matters for databases

NVMe storage answers small reads and writes with far lower latency than spinning disks and older SATA setups. Databases, search indexes and session stores do many small operations, so this is where NVMe shows. Large static media gains less and can live on cheaper storage elsewhere.

What to measure

ToolShowsScale up when
free -mUsed and available memoryAvailable memory stays near zero or swap grows
uptime, htopLoad average and CPULoad stays above the core count
iostat -xDisk waitAwait times climb at peak
Slow query logExpensive queriesQueries stay slow after indexing

Fix the cheap causes first: caching, indexes and heavy plugins. A faster query helps more than a bigger server.

A sensible starting method

  1. Start with a mid-size plan and the production stack under a realistic test.
  2. Record memory, load and disk wait at peak for a week.
  3. Move one step up only the resource that is actually saturated.

Compare plans on the cloud server page. For the basics of what you are renting, read what is a cloud server. When load is steady and heavy for months, a dedicated server may fit better.

Frequently asked questions

How much RAM does a WordPress shop need?

It depends on workers, plugins and traffic. Measure peak usage and add headroom rather than copying a number from a forum.

Is more vCPU always faster?

No. A single request runs on one core. More cores help only when requests run in parallel.

Do I need NVMe for a static site?

No. The gain shows with databases and many small reads and writes.

When should I scale up?

When a resource stays saturated at peak after you have fixed caching and queries.

high performance cloud kvm nvme vps eurovdc

EuroVDC

Discover the Power of Cloud

KVM virtualization · Instant scaling · 24/7 Support

Rent a Cloud Server

Author

Ergün KURT

08.07.2026

Was this article helpful?

– people found this helpful

Share on Social Media

High-Performance Cloud Server: CPU, RAM and NVMe