# How much RAM does my VPS need? A practical guide

> A practical RAM sizing table for common VPS workloads, from websites and Docker apps to blockchain nodes, mapped to DataPasa plans, with usage tips.

RAM is usually the first resource a small server runs out of. CPU that is too slow makes things wait, but a server without free memory starts swapping or the kernel kills processes, and your site goes down. The good news: most projects need less than people expect, and on DataPasa you pay by the hour, so trying a plan and moving to a bigger one later costs very little.

## What uses memory on a VPS

- **The operating system.** A minimal Ubuntu or Debian server uses a few hundred megabytes after boot.
- **Your application runtime.** PHP-FPM workers, Node.js, Python or Java processes. Java and Node.js tend to need the most.
- **Databases.** MySQL, MariaDB and PostgreSQL use RAM as cache. More memory means fewer disk reads.
- **Page cache.** Linux keeps recently read files in free memory. It is released when programs need it, so "used" memory that is really cache is not a problem.

## The DataPasa VPS plans

| Plan | vCPU | RAM | NVMe disk | Traffic |
|---|---|---|---|---|
| VPS-1 | 1 | 1 GB | 16 GB | 1 TB |
| VPS-2 | 1 | 2 GB | 32 GB | 32 TB |
| VPS-3 | 2 | 4 GB | 64 GB | 32 TB |
| VPS-4 | 4 | 8 GB | 128 GB | 32 TB |
| VPS-5 | 6 | 12 GB | 192 GB | 32 TB |
| VPS-6 | 6 | 16 GB | 256 GB | 32 TB |
| VPS-7 | 8 | 24 GB | 320 GB | 32 TB |

Current prices are on the [pricing page](https://datapasa.com/en/pricing).

## Sizing table by workload

These are practical starting points for a single project on one server. Busy sites, many users or several projects on one VPS need more.

| Workload | RAM to start with | Plan to start with |
|---|---|---|
| Static site, small reverse proxy, personal bot | 1 GB | VPS-1 |
| WordPress or another PHP site with MySQL, low traffic | 2 GB | VPS-2 |
| WordPress or WooCommerce with steady traffic | 4 GB | VPS-3 |
| A few Docker apps with Compose (monitoring, wiki, password manager) | 2 to 4 GB | VPS-2 or VPS-3 |
| AI agent such as OpenClaw with a cloud model | 2 GB | VPS-2 |
| Node.js or Python API with a database | 2 to 4 GB | VPS-2 or VPS-3 |
| GitLab, Nextcloud with many users or other heavy web apps | 8 GB | VPS-4 |
| Several production sites and databases on one server | 8 to 16 GB | VPS-4 to VPS-6 |
| Local 7B language model through [Ollama](https://datapasa.com/wiki/guides/run-ollama-on-cpu-vps) | 8 GB or more | VPS-4 or larger |
| [Celestia light node](https://datapasa.com/wiki/guides/run-celestia-light-node) | 1 GB | VPS-2 |
| LND Lightning node with Neutrino | 2 GB | VPS-2 |
| Pruned Bitcoin Core node | 2 GB, 4 GB for a faster first sync | VPS-3 |
| Pruned Monero node | 4 GB, more disk than RAM | VPS-5 |

Two notes about the table:

- **Disk can decide the plan, not RAM.** A pruned Monero node needs only about 4 GB of RAM, but around 110 GB of disk, which is why VPS-5 is the fit. Check disk needs as well.
- **Traffic matters for nodes and downloads.** VPS-1 includes 1 TB per month. A Bitcoin node downloads the whole chain once, which is more than that. Other plans include 32 TB.

For step by step setups see the guides for a [pruned Bitcoin node](https://datapasa.com/wiki/guides/run-pruned-bitcoin-node), a [Monero node](https://datapasa.com/wiki/guides/run-pruned-monero-node) and [OpenClaw](https://datapasa.com/wiki/guides/install-openclaw-on-vps).

> **Minecraft is a separate product.** For a Minecraft Java server you do not need to size a VPS at all. DataPasa game servers come with the Pterodactyl panel and plans with 2, 4 or 8 GB of RAM. Compare them in [how to choose a Minecraft server plan](https://datapasa.com/wiki/game-servers/choose-minecraft-server-plan), then follow [how to order a game server](https://datapasa.com/wiki/game-servers/order-a-game-server).

## How to check real memory usage

After your project runs for a day, look at the actual numbers:

```bash
free -h
```

Look at the **available** column, not **free**. Available includes cache that Linux can release at any moment. If available memory stays above 20 to 30% of the total under normal load, the plan fits.

To see which processes use the most memory:

```bash
ps aux --sort=-%mem | head -n 10
```

For Docker containers:

```bash
docker stats --no-stream
```

Signs that you need more RAM:

- `dmesg` or `journalctl -k` shows **Out of memory: Killed process**.
- The server is slow and swap usage keeps growing in `free -h`.
- Your database restarts under load.

## Add swap as a safety net

Swap is disk space used as overflow memory. It is much slower than RAM, but it can prevent a crash during a short spike, for example while `apt` or a build runs. Check whether swap exists with `swapon --show`. To add a 2 GB swap file:

```bash
fallocate -l 2G /swapfile
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile
echo '/swapfile none swap sw 0 0' >> /etc/fstab
```

Swap is a cushion, not a replacement. If the server uses swap all the time, move to a bigger plan.

## Start small, grow when needed

- **Start one plan lower if unsure.** Billing is hourly with no contract or minimum term, so testing costs little.
- **Watch it for a few days.** Real usage beats any table.
- **Move up when the numbers say so.** Set up the new server, move your data, then delete the old one to stop its billing.

Not sure which plan fits your project? Write to support@datapasa.com with what you plan to run and we will suggest one.

## Summary

For most personal projects 2 to 4 GB of RAM is enough, with VPS-2 and VPS-3 as the usual starting points. Heavier web apps and multi site servers need 8 GB and up, and blockchain nodes are often limited by disk and traffic more than by memory. Measure with `free -h`, keep a small swap file as a cushion and upgrade when the numbers tell you to.