Container memory (OOMKiller) resilience

What it does

This Scenario forces memory pressure in a pod to verify that Kubernetes terminates it before it consumes too much memory.

‍

Why it's recommended

The Linux operating system has an Out of Memory Manager (sometimes referred to as the OOMKiller) that kills processes when it detects that the system is out of memory. Some container runtimes, such as Kubernetes, have an additional OOMKiller that terminates container processes when they violate their memory resource limits. In both cases, the OOMKiller is a resilience mechanism, and this Scenario verifies that it works as intended.

You can use this Scenario to:

• Validate system stability and resiliency in preparation for high traffic events, like Black Friday, Cyber Monday, and other major sales holidays.
• Reduce operating expenses by optimizing infrastructure capacity based on application memory requirements.
• Streamline cloud migrations by simulating cloud conditions on-premises, such as noisy neighbors on shared infrastructure.

In addition to Kubernetes workloads, this Scenario can also help:

• Simulate memory-intensive workloads such as in-memory caches, databases, and machine learning models.
• Test performance when using disk swapping/paging.