{"id":923,"date":"2026-08-19T23:34:31","date_gmt":"2026-08-19T23:34:31","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=923"},"modified":"2026-08-19T23:34:31","modified_gmt":"2026-08-19T23:34:31","slug":"tune-linux-memory-swappiness-vps-performance","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/tune-linux-memory-swappiness-vps-performance\/","title":{"rendered":"How to Tune Linux Memory Swappiness for Better VPS Performance"},"content":{"rendered":"\n

vm.swappiness<\/code> is a single kernel parameter that many VPS guides tell you to change \u2014 usually to 10 \u2014 without explaining what it actually does or why the default of 60 is a poor fit for servers. It is not a “percentage of RAM that will be swapped.” It is a weighting the kernel uses when it must reclaim memory: how willing it is to evict anonymous (process) memory to swap versus dropping file-backed page cache. Get it wrong and you either swap under no real pressure (wasted disk I\/O) or starve the page cache (re-reads from disk). This guide shows how to measure, set, and verify swappiness for typical VPS workloads.<\/p>\n\n\n\n

What swappiness actually controls<\/h2>\n\n\n\n

When RAM is full, the kernel must reclaim memory from one of two main pools: page cache (clean copies of files on disk \u2014 cheap to drop, but re-reading costs I\/O) and anonymous pages (process heap and stack \u2014 they must be written to swap before the page can be reused, or the process gets killed by the OOM killer). The swappiness value, on a scale of 0 to 100, biases this choice: low values make the kernel prefer dropping page cache and avoid swapping anonymous memory; high values make it more willing to swap.<\/p>\n\n\n\n

The default of 60 was chosen for general-purpose desktops. On a server with a fixed workload, 60 makes the kernel swap pages that are cold but not frozen, producing extra disk I\/O for no benefit. One important correction: vm.swappiness=0<\/code> does not<\/em> disable swapping \u2014 the kernel can still swap to avoid OOM. That is why modern practice says use 1 rather than 0 when you want “as little swapping as possible.”<\/p>\n\n\n\n

Check your current value<\/h2>\n\n\n\n