Gremlin Scenario: Container CPU scalability

How it works

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.

Use cases

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.

Result

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.

Keep going

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.

Container CPU scalability