Diagnostic/Treatment
Pre-condition: You get the output from testIO.sh as explained in Required Data: IO.
The aim of this guide is providing minimum values for representative file sizes (and times) to consider a File System as healthy.
Write test
| File Size | Times | Min Healthy Values |
|---|---|---|
1K |
10000 |
1 M/s |
10K |
1000 |
5 M/s |
100K |
1000 |
100 M/s |
10M |
100 |
100 M/s |
50M |
10 |
100 M/s |
100M |
10 |
100 M/s |
Write/Read test
Minimum values for Write/Read are approximately the half of the listed ones in the Write test table. Please note that server throughput and latency time depends upon instance’s load as well. Ideally to get acquainted with your system, we recommend that you run execute testIO.sh after rebooting the instance as well as at peak load to get an idea about how the load is impacting its throughput.
This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.