2GB RAM VPS: What It Can and Can’t Run (and How to Get More Out of It)

A 2 GB RAM VPS is the entry-level sweet spot: cheap enough for a side project, powerful enough for real production traffic. But it has hard limits, and most “my server got slow” stories start at exactly this size. This guide covers what a 2 GB plan can and cannot run, the memory math that decides it, and the Linux tuning that squeezes noticeably more out of the same hardware.

Before tuning anything, look at what you can actually get for your money — see the full specs in our VPS comparison table. A 2 GB plan with NVMe storage and 2 vCPUs is a completely different machine than a 2 GB plan on shared spinning disks.

What runs comfortably on 2 GB

• WordPress or another PHP site with Nginx + PHP-FPM, tuned as shown below — a few thousand daily visitors is realistic.
• A Node.js, Python, or Go API — most JSON APIs idle below 150 MB and burst to a few hundred MB.
• A small database — MySQL/MariaDB/PostgreSQL with a working set under ~1 GB, e.g. a few hundred thousand rows.
• Network services — WireGuard VPN, Caddy or Nginx reverse proxy, DNS, a mail relay.
• 2–4 lightweight Docker containers (avoid running a JVM or Elasticsearch in there).
• Static sites, RSS aggregators, uptime monitors, analytics — anything that is mostly idle.

What does not fit

Elasticsearch with default heap settings (it wants 4 GB+), heavy CI runners, video transcoding, modded Minecraft servers, and multiple production databases are all out. The rule of thumb: if the application’s documentation lists a 4 GB minimum, do not fight it on 2 GB — you will spend your evenings debugging OOM kills instead of shipping features.

The memory math: PHP-FPM

PHP-FPM is where most 2 GB servers die. Each worker process holds one request in memory, so the number of concurrent visitors you can serve equals your workers. The formula: pm.max_children = usable RAM / average worker size. With 2 GB total, the OS and Nginx use ~300 MB, leaving ~1.7 GB. At 256 MB per worker (a typical WordPress memory limit), that is 6 workers. A sane www.conf setup:

pm = dynamic
pm.max_children = 6
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 3
pm.max_requests = 500

pm.max_requests = 500 recycles workers to stop memory leaks from accumulating. If your site uses object caching (Redis), give Redis 64–128 MB and reduce PHP’s memory limit to 128 MB per worker — that roughly doubles your concurrent capacity.

Swap and zram: your safety net

A little swap prevents OOM-killer surprises, but on SSD-backed VPS you want zram (compressed RAM) rather than a disk swapfile for the hot path. Enable it on Ubuntu 24.04:

apt install -y systemd-zram-generator
# /etc/systemd/zram-generator.conf
[zram0]
zram-size = ram / 2
compression-algorithm = zstd

systemctl daemon-reload
systemctl start systemd-zram-generator
swapon --show

Also lower swappiness so the kernel prefers caching over swapping: add vm.swappiness=10 to /etc/sysctl.d/99-swap.conf and run sysctl -p.

Quick wins for the database

MySQL/MariaDB defaults assume a bigger machine. On 2 GB, cap the buffer pool so the DB never competes with your app for RAM — in /etc/mysql/mariadb.conf.d/50-server.cnf:

[mysqld]
innodb_buffer_pool_size = 512M
innodb_log_file_size = 64M
max_connections = 50

512 MB is enough to cache several hundred MB of hot rows, and 50 connections covers a 6-worker PHP-FPM pool with headroom.

Workload	Works on 2 GB?	Notes
WordPress (tuned Nginx + PHP-FPM)	Yes	~6 concurrent PHP workers
Node/Python/Go API	Yes	Keep working set under 1 GB
Small MySQL/PostgreSQL	Yes, with tuning	Cap buffer pool at 512 MB
2–4 Docker containers	Yes	Avoid JVM-based images
Elasticsearch, big CI, video encode	No	Step up to 4 GB+

Know when to upgrade

Monitor with free -h, uptime, and dmesg | grep -i oom. If you see OOM kills or sustained swap usage during normal traffic, the workload has outgrown 2 GB — upgrade before the site degrades, not after an outage. Many providers let you resize in-place without reinstalling, so starting at 2 GB and growing is a low-risk strategy.

A 2 GB VPS is a genuinely capable machine when you respect its limits: tune PHP-FPM, cap the database, add zram, and it will serve real traffic all day. Compare VPS plans side by side to find a 2 GB plan with NVMe and a fair price, then apply this guide and skip the painful trial-and-error.