{"id":814,"date":"2026-08-06T22:54:12","date_gmt":"2026-08-06T22:54:12","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=814"},"modified":"2026-08-19T22:12:36","modified_gmt":"2026-08-19T22:12:36","slug":"vps-swap-space-swappiness-tuning-guide","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/vps-swap-space-swappiness-tuning-guide\/","title":{"rendered":"Swapfile vs zram on a VPS: Setup, Monitoring, and Swappiness"},"content":{"rendered":"\n

Swap is the emergency reservoir Linux uses when physical RAM runs out \u2014 and on a VPS it is either a lifesaver or the thing that makes your server feel ten times slower. The difference is not just how much swap you configure, but what kind: a swapfile on disk, a swap partition, or zram compressed RAM. This guide covers creating and enabling each, monitoring real swap pressure, and the swappiness defaults that keep the kernel from leaning on disk unnecessarily.<\/p>\n\n\n\n

Swapfile, partition, or zram?<\/h2>\n\n\n\n
Type<\/th>Speed<\/th>Best use case<\/th><\/tr><\/thead>
Swapfile<\/td>Disk I\/O speed<\/td>Default choice on VPSes; easy to create and resize<\/td><\/tr>
Swap partition<\/td>Disk I\/O speed<\/td>Only if the provider image already includes one; hard to resize<\/td><\/tr>
zram<\/td>RAM speed (compressed)<\/td>Small VPS with tight disk I\/O; bursty memory spikes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

A swapfile costs nothing until used and takes minutes to create on any filesystem that supports it (ext4, xfs, btrfs). A partition requires repartitioning the disk, which most VPS control panels make awkward. zram uses a slice of RAM compressed roughly 2\u20134x, so it never touches disk \u2014 at the cost of some CPU and usable RAM.<\/p>\n\n\n\n

Creating a swapfile<\/h2>\n\n\n\n
    \n
  1. Check existing swap: swapon --show<\/code> (empty output = none) and free -h<\/code>.<\/li>\n
  2. Create the file: sudo fallocate -l 2G \/swapfile<\/code>. If fallocate<\/code> fails on your filesystem, use sudo dd if=\/dev\/zero of=\/swapfile bs=1M count=2048 status=progress<\/code>.<\/li>\n
  3. Restrict permissions: sudo chmod 600 \/swapfile<\/code> \u2014 world-readable swap can expose credentials that were swapped out.<\/li>\n
  4. Format it: sudo mkswap \/swapfile<\/code><\/li>\n
  5. Enable it: sudo swapon \/swapfile<\/code><\/li>\n
  6. Make it persistent: add \/swapfile none swap sw 0 0<\/code> to \/etc\/fstab<\/code>.<\/li>\n
  7. Verify: sudo swapon --show<\/code> and free -h<\/code> \u2014 the Swap line should show your new size.<\/li>\n<\/ol>\n\n\n\n

    How much swap is enough<\/h2>\n\n\n\n

    The old “2x RAM” rule is wrong for VPSes. Swap on a small plan shares disk I\/O with your real workload, so oversized swap turns a memory crisis into a disk crisis. Practical sizing: 1\u20132 GB on plans up to 4 GB RAM \u2014 enough to ride out spikes and keep the OOM killer idle \u2014 and 2\u20134 GB on larger plans for safety. If an application consistently needs more than that, buy more RAM instead: swap is a safety net, not a RAM upgrade.<\/p>\n\n\n\n

    zram: compressed swap in RAM<\/h2>\n\n\n\n
      \n
    1. Install: sudo apt install -y zram-tools<\/code> (Debian\/Ubuntu).<\/li>\n
    2. Configure \/etc\/default\/zramswap<\/code>: set ALGO=zstd<\/code> and SIZE=1024<\/code> (MiB) \u2014 start at about half your free RAM.<\/li>\n
    3. Start it: sudo systemctl enable --now zramswap<\/code><\/li>\n
    4. Verify: swapon --show<\/code> should list \/dev\/zram0<\/code>.<\/li>\n<\/ol>\n\n\n\n

      zram shines on small VPSes where a memory spike would otherwise push pages to a shared disk: the “swap” stays in RAM, so recovering from a spike is fast. It is a poor fit when you genuinely need more memory than the box has \u2014 for example a database larger than RAM \u2014 because then disk swap is the only option and the right fix is a bigger plan.<\/p>\n\n\n\n

      Monitoring swap pressure<\/h2>\n\n\n\n