I'm familiar with AppMon's calculation of i/o:
i/o = Response Time - CPU - Sync - Runtime Suspension - Wait
However, this is calculated on a per PurePath basis.
I am working with a customer and saw the following CPU graph. In this case I wasn't able to articulate precisely what was causing this high I/O Wait time.
It is an Amazon Linux host.
Any help/descriptions would be greatly appreciated.
Solved! Go to Solution.
Hi @Michael K., we experience the same alert. Do you think that the status "CPU Saturation" is correct in case of IOWait - which is - as far as I know - a state of Idle. That said - additional workload could still be accepted by the CPU - or am I wrong?