Linux guides

Inspect, configure, and tune as separate decisions

Linux memory work is easier to maintain when three questions remain separate: what is already running, whether the backing arrangement is suitable, and whether a policy change improves the workload. Do not make a new swap file, add compression, and alter swappiness in the same unexplained experiment.

Start with the Linux Mem Swap overview. The swap-file article then provides a deliberately scoped ext4 example with verification and persistence checkpoints. The swappiness article explains how to test a policy hypothesis without treating the value as a RAM-fullness percentage. The compressed-memory comparison distinguishes zram from zswap and focuses on the complete resource path.

Record the active areas, the owning service or configuration system, and the baseline workload before editing anything. Keep a recovery path for disruptive changes and do not assume ordinary swap activation establishes hibernation support.

Readers working inside containers should also visit Cloud Mem Swap. A container's effective limits can matter even when the surrounding host has capacity. Understanding the boundary is part of the Linux diagnosis, not an optional detail added after a configuration fails.