You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perfcount description describe that:
"the scale is seconds, the counter has millisecond precision, meaning a value of 0.004 indicates the average time for disk transfers to complete was 4 milliseconds."
Full description is:
"Avg. Disk sec/Transfer (Avg. Disk sec/Read, Avg. Disk sec/Write)
Displays the average time the disk transfers took to complete, in seconds. Although the scale is seconds, the counter has millisecond precision, meaning a value of 0.004 indicates the average time for disk transfers to complete was 4 milliseconds.
This is the counter in Perfmon used to measure IO latency.
I wrote a blog specifically about measuring latency with Perfmon. For details got to “Measuring Disk Latency with Windows Performance Monitor”.
Source: https://blogs.technet.microsoft.com/askcore/2012/03/16/windows-performance-monitor-disk-counters-explained/
And in other source(on russian), as in the previous one, the authors recommend to pay attention and add two triggers:
one is ...\Avg. Disk sec/Write].last()}>0.005 , level-high
second is ...\Avg. Disk sec/Write].last()}>0.0025, level-medium
and another "Less than 10 milliseconds is good and more than 20 milliseconds is bad”
For this reason, could you fix a few requests, Please:
Measurment units(Bps to ms) in the vertical axis of the grid;
In graph keywords, ms units instead of Bps;
Add two triggers with red and yellow color if its possible.
Thanks
The text was updated successfully, but these errors were encountered:
About Disk IO.
Screenshoot from my zabbix board: https://snag.gy/Gjku5U.jpg
Perfcount description describe that:
"the scale is seconds, the counter has millisecond precision, meaning a value of 0.004 indicates the average time for disk transfers to complete was 4 milliseconds."
Full description is:
"Avg. Disk sec/Transfer (Avg. Disk sec/Read, Avg. Disk sec/Write)
Displays the average time the disk transfers took to complete, in seconds. Although the scale is seconds, the counter has millisecond precision, meaning a value of 0.004 indicates the average time for disk transfers to complete was 4 milliseconds.
This is the counter in Perfmon used to measure IO latency.
I wrote a blog specifically about measuring latency with Perfmon. For details got to “Measuring Disk Latency with Windows Performance Monitor”.
Source: https://blogs.technet.microsoft.com/askcore/2012/03/16/windows-performance-monitor-disk-counters-explained/
And in other source(on russian), as in the previous one, the authors recommend to pay attention and add two triggers:
one is ...\Avg. Disk sec/Write].last()}>0.005 , level-high
second is ...\Avg. Disk sec/Write].last()}>0.0025, level-medium
and another "Less than 10 milliseconds is good and more than 20 milliseconds is bad”
For this reason, could you fix a few requests, Please:
Thanks
The text was updated successfully, but these errors were encountered: