OOM

In computing, OOM (Out-Of-Memory) refers to a condition in which a system is unable to allocate additional memory for a process or operation, typically due to exhaustion of available physical memory and swap space. This phenomenon is critical in operating systems, particularly in environments where resource constraints can lead to application instability or system-wide failures. The OOM killer, a feature in the Linux kernel, is designed to mitigate such situations by terminating processes that consume excessive memory, thereby preventing the system from becoming unresponsive.

Definition and Function

OOM is a common issue in systems with limited memory resources. When a process requests more memory than is available, the kernel may invoke the OOM killer to terminate the most resource-intensive process, prioritizing the stability of the system over the individual process. This mechanism is particularly relevant in server environments, embedded systems, and other scenarios where memory usage must be tightly controlled. The decision criteria for the OOM killer include factors such as the memory consumption of the process, its priority, and the potential impact of its termination on system functionality.

Systemd Integration

In Linux distributions using systemd, memory management and OOM handling are further refined through service unit configurations. The systemd.exec(5) and systemd.scope(5) man pages provide detailed guidance on configuring memory limits for services and scopes, which can influence how the OOM killer behaves. For example, the `MemoryMax` directive in service units allows administrators to set hard limits on memory usage, potentially preventing processes from reaching a state that would trigger OOM conditions. These configurations are essential for ensuring predictable system behavior under memory pressure.

Configuration and Tuning

Tuning OOM behavior often involves adjusting kernel parameters and systemd service configurations. Key parameters include `vm.overcommit_memory`, which controls how the kernel handles memory overcommitments, and `oom_kill_allocating_task`, which determines whether the OOM killer targets the process that triggered the memory exhaustion. Systemd-specific settings, such as `MemoryAccounting` and `LimitMemory`, further enable granular control over resource allocation. These adjustments require careful consideration to balance system stability with application performance.

References

- [systemd.exec(5)](https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html) – Detailed documentation on systemd service execution parameters. - [systemd.scope(5)](https://www.freedesktop.org/software/systemd/man/latest/systemd.scope.html) – Information on systemd scope units and memory management. - Technical articles in this category are applicable to Linux. Debian GNU/Linux is used in examples. Much of the information is also applicable to other Linux distributions and Unix flavours.

This page contains information generated by Ollama. The information was reviewed, and may have been altered, by a human editor before being added to the Featured category. As of July 2026 information generated by AI is not subject to copyright and is thus in the public domain. This page is pending human review.