3 ms·
Best i can tell after some quick glancing on the history of the metric, the value of including IOWait depends more on the hardware than the software. If your I
by digi_owl 11y ago
Best i can tell after some quick glancing on the history of the metric, the value of including IOWait depends more on the hardware than the software.
If your IO actions are performed by CPU rather than DMA, having them in there makes sense (it will slow down anything else). but if it is performed via DMA (or in other ways offloaded from the CPU) it makes less sense.
- jws 11y agoGenerally, processes in IOWait are not running, they are sitting around in a queue waiting for their data. Anyone waiting on the process is feeling pain, but it isn't eating any CPU so it comes down to what you want the metric to mean. Should it reflect user discomfort or consumption of cpu cycles.
- digi_owl 11y agoYes the process is sleeping, but the system (OS and hardware) is still active doing whatever IO was requested.
- mnw21cam 11y agoThe reason load average typically included processes stuck in IOwait is because there are several systems that decide whether or not to start more processes depending on what the load average is. One of these is make, and you will also get people manually looking at load average to work out whether a machine can handle some more work. When a machine runs out of RAM and starts thrashing, it most definitely does not want to have more stuff run on it. You want the load average to be high in this case to discourage people or programs from starting more stuff. Luckily, when a system starts thrashing, it typically has lots of processes in IOwait, so load average goes through the roof.