VPS RAM Requirements: How Much RAM and CPU Does Your VPS Need?

VPS RAM requirements depend on what runs on your server: the operating system, the web server, PHP or Node.js, the database and any cache. Buy too little and checkout crashes in the middle of a sale. Buy too much and you pay every month for memory nobody uses.

Below, we size a VPS by workload: WordPress, WooCommerce, MySQL, Node.js and cPanel. Where an official requirement exists, we quote it and link the source. Where it doesn't, we give an estimate and say so.

Still not sure you need a VPS at all? Read our shared hosting vs VPS comparison first, then come back here to size it.

Bottom line: For many small sites, 2GB RAM with 1–2 vCPU is a typical starting point. A basic WordPress blog with good caching can run on 1GB, but it has little headroom. WooCommerce stores, and sites that run their own database plus extra services, commonly start at 4GB RAM and 2 vCPU. These are starting points, not guarantees: traffic, plugins and concurrent requests decide the real number, so watch usage for two weeks and resize.

Key takeaways

• RAM decides how many things your server can do at once. The CPU decides how fast each task finishes.

• Your VPS RAM must cover the OS, web server, PHP or Node.js, the database and a cache — not just your app.

• WooCommerce asks for a WordPress memory limit of 256MB or more (WooCommerce docs). That is a per-process limit, not your total server RAM.

• Swap is a safety net, not extra RAM.

• Start small, measure, then upgrade. Most VPS plans scale up easily.

How Much RAM Do I Need for a VPS?

Short answer: It depends on what runs on the server, not on your visitor count alone. Add up every service, then leave 20–30% free for spikes.

Think of RAM like desk space. Every program you open takes a corner of the desk. The operating system, Nginx or Apache, PHP, MySQL and Redis all need their own space. When the desk is full, Linux starts pushing work to disk (swap), and everything slows down. If memory still runs out, the kernel's OOM killer stops a process — often your database.

So the real question is: what will live on this desk?

VPS sizing guide by workload

The table below shows typical starting points for a Linux VPS with a lightweight stack. These are our working estimates, not official minimums from WordPress, MySQL or Node.js, and not capacity guarantees. You may need more RAM for high traffic, many plugins, lots of concurrent requests or a control panel such as cPanel.

Why the database changes everything

MySQL keeps hot data in RAM in an area called the InnoDB buffer pool. By default that pool is 128MB (MySQL 8.4 Reference Manual). That default is small on purpose, so MySQL can start on a tiny server.

As your tables grow, a bigger buffer pool means fewer slow disk reads. MySQL's own optional auto-tuning (innodb_dedicated_server) sets the pool to about half of RAM on a 1–4GB machine — but only on servers that run nothing but MySQL. On a shared web + database VPS, you'll want a smaller share so PHP still has room.

How much RAM does a Node.js app need?

Short answer: A small Express API often fits on a 1–2GB VPS. A full MERN app with MongoDB on the same server is safer at 4GB.

Node.js itself is light. Memory grows with what your app keeps in memory: sessions, caches and large JSON payloads. Process managers like PM2 in cluster mode start one Node.js process per core, and each process has its own V8 heap. Two processes mean roughly twice the memory.

V8 picks its heap limit from the memory it detects. You can cap it with the --max-old-space-size flag so one leaky process can't starve the database (Node.js memory guide). Planning a MERN deployment? See our MERN stack hosting options.

Do control panels change the math?

Yes, a lot. The official cPanel & WHM requirements list 2GB RAM minimum and 4GB recommended, and the installer stops if the server has too little (cPanel system requirements). So a 1GB VPS can't run cPanel at all, and a 2GB one leaves very little for your sites.

How Many CPU Cores Do You Need for a VPS?

Short answer: 1 vCPU is fine for a light, well-cached site. Choose 2 vCPU for WordPress with a database on the same server, and 4 or more for stores, multiple sites or build-heavy apps.

A vCPU is a virtual slice of a physical processor core. More vCPUs let the server handle more requests at the same moment. For PHP sites, each uncached page view keeps a PHP worker busy, and each busy worker uses a CPU thread while it runs.

Picture a shop. RAM is how many customers fit inside; CPU is how many cashiers are on duty. A big shop with one cashier still has a long queue.

Signs you need more CPU, not RAM

• Load average stays above your vCPU count for long periods.

• Pages are slow, but free -m still shows plenty of free memory.

• Backups, image resizing or WooCommerce imports freeze the site.

Signs you need more RAM, not CPU

• Swap usage keeps climbing.

• MySQL or PHP-FPM restarts on its own (an OOM kill).

• You see "Allowed memory size exhausted" errors, even after raising PHP limits.

Do you need to swap on a VPS?

Yes, a small swap file is a sensible safety net, especially on 1GB and 2GB plans. It catches short memory spikes instead of letting a process crash. But swap lives on disk, so it is far slower than RAM. If your server uses swap all day, that's a clear sign to upgrade — not to add more swap.

What VPS Specs Do I Need for a WordPress Site?

Short answer: Many business WordPress sites start well on 2GB RAM and 2 vCPU, with PHP 8.4 or 8.5, MySQL 8.4 LTS or a supported MariaDB LTS release, HTTPS and page caching. WooCommerce stores commonly start at 4GB RAM or more. Your traffic and plugins decide the final number.

Official WordPress requirements

WordPress publishes two sets of guidance, and they don't say exactly the same thing. The WordPress requirements page still lists PHP 8.3+, MySQL 8.0+ or MariaDB 10.11+, and HTTPS (checked 29 Oct 2026). The Hosting Team's newer WordPress 7.1 server compatibility guide goes further. For new installations, it recommends:

Our advice: on a new VPS, install MySQL 8.4 LTS or a supported MariaDB LTS release, not MySQL 8.0. Versions and end-of-life dates change, so check the compatibility guide on the day you deploy.

Notice what's missing: a RAM number. WordPress does not publish a total server RAM requirement. That's why sizing guides like this one exist.

Read Our Full Guide: WordPress Hosting Requirements For You

WooCommerce VPS requirements

WooCommerce publishes stricter guidance. For WooCommerce 10.8 and later, it lists a WordPress memory limit of 256MB or greater, plus HTTPS and specific SQL modes (WooCommerce Server Recommendations). Requirements change between releases, so check the page before you build.

One point confuses many buyers. That 256MB is the most memory one PHP process may use. It is not the RAM your VPS needs. If four PHP workers each hit 256MB at once, that alone is about 1GB — before MySQL, the OS or Redis take their share.

What actually drives WordPress RAM use

• PHP workers. PHP-FPM's pm.max_children setting decides how many run at once. A rough cap is the RAM you can spare for PHP divided by your average worker size, which you can read in htop.

• MySQL buffer pool. Bigger databases want more RAM for speed.

• Caching. Page caching (LiteSpeed Cache, WP Rocket, Nginx FastCGI cache) cuts PHP work sharply. Redis or Memcached object caching saves database queries but uses RAM itself.

• Plugins. Page builders, security scanners and backup plugins are often the heaviest.

• Uncacheable pages. WooCommerce cart, checkout and My Account pages must stay out of the page cache, so every visit there hits PHP and MySQL.

Quick tip: In WordPress, go to WooCommerce → Status (for stores) or Tools → Site Health → Info to see your current PHP version, memory limit and database version.

1GB vs 2GB vs 4GB VPS: Which One Is Right for You?

Short answer: As a rough guide, 1GB suits testing and tiny static sites, 2GB often covers one small business or WordPress site, and 4GB is a common starting point for WooCommerce, MERN apps or several sites on one server. Treat these as typical starting points, not fixed rules: traffic, plugins, concurrent requests and a control panel can all push the number up.

Is a 2GB VPS enough for a small business site?

For most brochure sites, yes. A 2GB VPS with page caching can serve a typical small business site comfortably, because cached pages barely touch PHP or MySQL. It stops being enough when you add things that can't be cached: online ordering, member logins, a busy contact form with heavy plugins, or a control panel like cPanel. If two or more of those apply to you, start at 4GB and save yourself a migration later.

When does a 1GB RAM VPS make sense?

A 1GB VPS is fine if you can manage Linux yourself and keep the stack lean — Nginx, PHP-FPM with few workers, a tuned database and a swap file. It's a learning box or a side project server. For a site that earns money, the small saving rarely justifies the risk of crashes.

What fits on a 4GB VPS?

A 4GB plan gives you room to run a full stack properly: web server, PHP, MySQL with a healthy buffer pool, Redis, and backups — all at once. It's the common starting point for WooCommerce stores and agencies hosting a few client sites.

How UmmahHost plans map to these sizes

UmmahHost lists these KVM-based plans (prices and specs checked on ummahhost.com on 29 Oct 2026 — confirm current pricing before you order):

If your visitors are mostly in Bangladesh, a BDIX VPS keeps traffic on the local exchange. If they're spread across countries, a Global VPS location closer to them is usually the better pick. 

How Do You Size a VPS? A 5-Step Method

Short answer: List your services, add up their memory, add 20–30% headroom, pick the nearest plan, then measure and adjust.

1. List everything that will run. Write down the web server, PHP or Node.js, database, cache, control panel, cron jobs and backup tools. Forgotten services are the top reason servers run out of memory.

2. Check your current usage. On an existing server, run free -m and htop during a busy hour. On shared hosting, check the resource graphs in cPanel. Real numbers beat any guide, including this one.

3. Add headroom. Add 20–30% on top of your peak for traffic spikes, plugin updates and backups.

4. Match CPU to RAM. Pair 2GB with at least 1 vCPU, and 4GB with 2 vCPU. Uncached PHP pages and imports are CPU-hungry.

5. Monitor for two weeks, then resize. Watch swap use, load average and OOM events. Upgrade if swap grows daily; downgrade if RAM sits below 40% for weeks.

Need help with the numbers? A managed VPS puts the tuning and monitoring in an engineer's hands instead of yours.

Worked Example: Sizing a WooCommerce Store in Dhaka

Imagine a clothing shop in Dhaka moving its WooCommerce store off shared hosting. It has about 800 products, and most buyers are in Bangladesh. During Eid sales, the old host kept showing memory errors at checkout.

Here's a rough memory budget for its new VPS. Every figure is an estimate; real use depends on the theme and plugins.

On a 2GB plan, that leaves almost no headroom — one backup job during a sale could push it into swap. Adding 30% headroom gives about 2.3GB, so the sensible pick is a 4GB RAM, 2 vCPU plan, such as BDIX Gold for a mostly local audience.

Notice the method, not just the answer: the store was sized for its Eid-sale peak, when checkout traffic can't be cached, rather than for a quiet weekday.

Explore How to Choose a Web Hosting Plan in 2026