Gremlin Scenario: Windows memory scalability

How it works

How this Scenario works

This Scenario progressively consumes memory on your Windows Server hosts in three stages: 50%, 75%, and 90%. This simulates memory pressure from traffic spikes, memory leaks, or under-provisioned instances.

Use cases

Why run this Scenario?

Identify memory leaks or poor resource management in .NET and IIS-based applications.
Test how Windows handles memory pressure and page file usage under extreme conditions.
Verify that Windows Performance Monitor and alerting tools detect memory pressure before exhaustion.
Optimize Windows host memory provisioning to balance cost and performance for your workloads.

Result

What to expect when you run it

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

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.

Windows memory scalability