Recommended Scenario
Container memory scalability
Verify that your containerized service scales as expected when memory is limited. Gremlin increases memory utilization in three stages—50%, 75%, and 90%—to validate container memory management.
Experiment types
Memory
Targets
Containers
Length
20 minutes
How it works
How this Scenario works
This Scenario progressively consumes memory within your containers in three stages: 50%, 75%, and 90%. This simulates memory pressure from traffic spikes, memory leaks, or under-provisioned container resource limits.
Use cases
Why run this Scenario?
- Identify memory leaks or poor garbage collection within containerized applications.
- Test how container memory limits interact with the container runtime under extreme pressure.
- Verify that container health checks and restart policies respond appropriately to memory exhaustion.
- Optimize container memory resource limits to balance cost, performance, and resilience.
Result
What to expect when you run it
If memory usage spikes to 90% within a container, the application continues to function without performance degradation for at least 5 minutes.
Keep going
More Scenarios to try
Avoid downtime. Use Gremlin to turn failure into resilience.
Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.
.svg)