It would be of great benefit if we could have FioLogParser automatically detect and separate IO traces into two series of data for reads and writes respectively. Perhaps we could visualize them with different colors or build separate graphs for these?
Recall that the output in Fio log files follows the format: time (msec), value, data direction, block size (bytes), offset (bytes), command priority
The data direction indicates whether the IO was a read (0), write (1), or trim (2).
Note that this should be designed so it can be toggled on/off by need with a new flag - for instance --separate-ios
These changes can affect multiple parts of the FioLogParser since parsing is currently implemented separately per mode. For now only fiohistogram and fio-ios are relevant for this change.
It would be of great benefit if we could have FioLogParser automatically detect and separate IO traces into two series of data for reads and writes respectively. Perhaps we could visualize them with different colors or build separate graphs for these?
Recall that the output in Fio log files follows the format: time (msec), value, data direction, block size (bytes), offset (bytes), command priority
The data direction indicates whether the IO was a read (0), write (1), or trim (2).
Note that this should be designed so it can be toggled on/off by need with a new flag - for instance
--separate-iosThese changes can affect multiple parts of the FioLogParser since parsing is currently implemented separately per mode. For now only fiohistogram and fio-ios are relevant for this change.