Disk I/O scalability

Description

Test that your service scales as expected when Disk I/O is limited. Gremlin will carry out many read and write operations in the target's /var/tmp directory. Estimated test length: 20 minutes.

Hypothesis

If disk I/O latency increases (e.g., by 50 ms), the service can still process incoming requests within SLA limits.

Why run this Scenario?

Storage is a finite resource that, when exhausted, can have unpredictable and potentially catastrophic effects on your systems. When applications and services can no longer write to disk, they might stop accepting new requests, go into an automatic suspend state, or crash. If a large file transfer is hogging up IOPS, applications that use disk may slow down, causing system-wide latency. Completing this Scenario demonstrates that your applications can tolerate low disk space and latency without failure.

  • Identify bottlenecks in database-heavy workloads.
  • Understand impact of slow persistent storage on services.
  • Test logging and metric systems under I/O pressure.
Target
Containers
Containers
Kubernetes
Linux
Linux
Microsoft Windows
Windows
Experiments
IO
IO
Preview
Runtime:  
20 minutes