Linux Mem Swap

Identify the arrangement already running

A Linux system may use a swap partition, a swap file, a compressed zram device, zswap in front of backing swap, or a combination. Before making changes, find out which configuration exists and which service or administrator owns it.

Start with read-only inspection:

swapon --show
free -h
sysctl vm.swappiness

The first command identifies active areas, the second provides a memory overview, and the third reports the current policy setting. None of these observations alone establishes that performance is good or bad. Compare them with a representative workload and the actual symptom.

Configure a file deliberately

A swap file needs a suitable filesystem, allocated backing blocks, restrictive permissions, successful activation, and a coherent persistence mechanism. Copy-on-write and sparse-file behavior make filesystem compatibility important.

Our Linux swap-file setup guide uses a narrowly scoped local ext4 example. It includes exclusive creation to avoid overwriting an existing path, verification before persistence, and a reminder that hibernation is a separate configuration problem.

Do not apply that recipe unchanged to Btrfs, network filesystems, or unfamiliar managed systems. Stop after an error, inspect the specific cause, and preserve the original configuration and recovery path.

Treat swappiness as a separate experiment

Swappiness is not the percentage of RAM that must be full before swap begins. Modern kernel documentation describes it as a 0–200 relative I/O-cost policy input. Setting it to zero is not the same as disabling swap.

A useful test begins with a workload objective and an observed problem. Record the baseline, make one temporary change, compare realistic runs, and restore the original value when the experiment ends unless the result is accepted.

The swappiness guide explains how to record benefits and regressions without promoting a universal “best” value.

Understand compressed memory before stacking features

zram can expose a compressed RAM-backed block device used as swap. zswap is a compressed cache in front of a backing swap area. Their configured capacities and physical resource costs should not be interpreted as the same measurement.

Read the zram versus zswap comparison before changing an existing distribution policy. Evaluate complete arrangements, including CPU work, storage behavior, startup configuration, and observability. Compression is not a guaranteed multiplication of installed RAM.

For containerized workloads, also inspect the effective resource hierarchy. The cloud and container guide distinguishes host capacity from cgroup memory and swap controls.

Technical references: The swapon manual covers activation restrictions; the kernel swappiness reference defines the policy scale.