Linux systems guides

Keep the Linux resource path understandable

These articles connect Linux swap configuration with policy, compressed memory, and workload limits. They are most useful when read against a small inventory of the system: kernel and distribution, active swap areas, filesystem, configuration owner, and the workload producing the symptom.

The Linux Mem Swap guide offers the entry point. The swap-file article covers suitability, creation, activation, and persistence. The swappiness article treats tuning as a controlled experiment. The zram-versus-zswap article explains why a compressed block device and a compressed swap cache should not be collapsed into one feature name.

Cloud readers can add the container-limits article to understand why host capacity and group allowance need separate observations. Locate the correct process group before interpreting a usage file, and preserve counter changes over the interval of the incident.

Keep one configuration mechanism responsible for each setting. Record a rollback and verify effective state after a planned restart or replacement. A configuration that can be inspected, explained, and reproduced is more useful than a set of copied commands with no documented purpose.