Container CPU scalability
Test that your service scales as expected when CPU capacity is limited. Gremlin will consume CPU in 3 stages: 50%, 75%, and 90%.
Experiment types
CPU
Targets
Containers
Length
15 minutes
How this Scenario works
This Scenario progressively consumes CPU within your containers in three stages: 50%, 75%, and 90%. This simulates CPU contention from resource-intensive workloads or under-provisioned container resource limits.
Why run this Scenario?
- Validate that container CPU resource limits are configured correctly and prevent resource starvation.
- Verify that container health checks and orchestration detect CPU pressure and trigger appropriate responses.
- Test how container resource limits interact with the host's CPU capacity under load.
- Identify containers that are under-provisioned for CPU before they cause production performance issues.
What to expect when you run it
As CPU usage increases within containers, the container runtime and orchestration layer automatically scale based on the thresholds you've set.
More Scenarios to try
Kubernetes packet loss
Ensure your Kubernetes systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate liveness/readiness probe and load balancer behavior.
Container packet loss
Ensure your containerized systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.
Windows packet loss
Ensure your Windows systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.
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)