I have set my cpu, network and disk activity as graphs.
The problem is that the disk activity can grow >100% when multiple disks are attached (like 200% when copying large files from one to the other hdd). When the io activity drops to 100% because one disk is slower than the other, the graph looks like this:

and the spikes beyond 100% are cut off.

That also happens to the network-IO
My suggestion would be to ensure that the max value is always in scale and maybe lock that scale to multiples of 100%
I have set my cpu, network and disk activity as graphs.


The problem is that the disk activity can grow >100% when multiple disks are attached (like 200% when copying large files from one to the other hdd). When the io activity drops to 100% because one disk is slower than the other, the graph looks like this:
and the spikes beyond 100% are cut off.
That also happens to the network-IO
My suggestion would be to ensure that the max value is always in scale and maybe lock that scale to multiples of 100%