Container memory scalability

Description

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.

What this Scenario does

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.

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.

Expected outcome

If memory usage spikes to 90% within a container, the application continues to function without performance degradation for at least 5 minutes.

Target
Containers
Containers
Experiments
Memory
Memory
Preview
Runtime:  
20 minutes