Bobcares

Perfmon counters for Disk Usage – Top Perfmon counters

by | Feb 24, 2021

Wondering how to use Perfmon counters for Disk Usage? We can help you.

Problems regarding Disk I/O are usually difficult to diagnose and debug. Perfmon disk counters help us to diagnose disk issues.

Here a Bobcares, we use perfmon counters as a part of our Server Management System for our customers using SQL.

Today let’s see some top performance counters to identify SQL server disk bottleneck.

Perfmon counters to identify SQL server disk bottleneck

We will see some top counters that are used by our Support Techs to identify the disk usage of a SQL server.

The values for all disk counters can split into three categories – Excellent, Good, and Poor.

Excellent – Disk Subsystem is responding perfectly for the respective counter.
Good – Disk Subsystem is responding fairly for respective counter and can be considered good considering your workload and other resource utilization.
Poor – Disk Subsystem is not responding well for respective counter and it requires your intervention to drill down more to understand the reason behind slowness.

Important perfmon disk counters are given below:

1. Average Disk Sec/Read

2. Average Disk Sec/Write

3. Average Disk Sec/Transfer

4. Average Disk Queue Length

5. Current Disk Queue Length

6. Disk Read/Sec and Disk Write/Sec

7. %Disk Time

8. %Idle Time

1. Average Disk Sec/Read

Average Disk Sec/Read is an important perfmon disk counter that shows the average time in seconds that is needed to read data from the disk. Also, it explains the disk latency.

We can find these counters at the logical and physical disk object level. The value for this counter is generally the number of seconds it takes to do each read. The shorter the time needed to read or write data, the faster the system.

If we get a counter value of more than 20ms, it means that our disk is not performing well.

The disk performance is:

Excellent, if the value of this counter is less than 6 milliseconds (0.006 sec)
Good, if the value of this counter is up to 15 milliseconds (0.015 sec)
Poor, if the value is constantly more than 15 milliseconds (0.015 sec)

2. Average Disk Sec/Write

Average Disk Sec/Write is also an important counter that shows the average time in seconds that is needed to write data to disk. Also, it explains the disk latency.

This counter can be tracked at the logical and physical disk level. The value for this counter is generally the number of seconds it takes to do each read. The shorter the time needed to read or write data, the faster the system.

If we constantly get a counter value of more than 20ms then it means our disk is not performing well.

The disk performance is:

Excellent, if the value of this counter is less than 6 milliseconds
Good, if the value of this counter is up to 15 milliseconds
Poor, if the value is constantly more than 15 milliseconds.

3. Average Disk Sec/Transfer

Average Disk Sec/Transfer is a time that measures average latency for read or write operations.

If the Average Disk Sec/Transfer value increases, this indicates that the I/O subsystem is not optimally keeping up with the I/O demand.

This counter is available under the Logical Disk and Physical Disk object.

The disk performance is:

Excellent, if the value of this counter is less than 6 milliseconds
Good, if the value of this counter is up to 15 milliseconds
Poor, if the value is constantly more than 15 milliseconds.

4. Average Disk Queue Length

Average Disk Queue Length counter shows us the average number of read and write requests that were queued on the selected physical disk.

If this value is exceeding its threshold frequently then we should also look at other perfmon disk counters Average Disk Read Queue Length and Average Disk Write Queue Length.

This helps us to diagnose whether the Average Disk Queue Length is high due to high read or high write operation. The recommended value for this counter is less than 2 per individual disk.

The disk performance is:

Excellent, if the value of this counter is less than 1.5 per drive.
Good, if the value of this counter is up to 2 per drive.
Poor, if the value is constantly more than 2 per drive.

5. Current Disk Queue Length

Current Disk Queue Length is the number of disk requests that are currently waiting as well as requests currently being serviced.

The difference between average disk queue length and current queue length is CDQL tells current load whereas ADQL tells load during a given time frame.

The Current Disk Queue Length metric in Windows Performance Monitor is available for both physical and logical disk. The Current Disk Queue Length value should be less than 2 per disk.

The disk performance is:

Excellent, if the value of this counter is less than 1.5 per drive.
Good, if the value of this counter is up to 2 per drive.
Poor, if the value is constantly more than 2 per drive.

6. Disk Read/Sec and Disk Write/Sec

Disk Reads/sec and Disk Writes/Sec shows us the number of read and write operations happening per second on the disk. If we want to benchmark disk capacity we can do it by gradually increasing the load on the system.

The disk performance is:

Excellent, if the value of this counter is less than 75% of total disk capacity.
Good, if the value of this counter is up to 85% of total disk capacity.
Poor, if the value is constantly more than 85% of total disk capacity.

7. %Disk Time

%Disk Time counter tells us how busy the disk is in performing read and write operations.

It shows the values as a normal one even the disk has a serious disk performance issue. So we should compare its value with the current/average disk queue length before reaching to any conclusion about disk issue.

The disk performance is:

Excellent, if the value of this counter is less than 75% of total disk capacity.
Good, if the value of this counter is up to 85% of total disk capacity.
Poor, if the value is constantly more than 85% of total disk capacity.

8. %Idle Time

%Idle Time measures the percentage of time the disk was idle during the sample interval.

The disk is idle when it is not processing any read and write requests.

If we constantly get its value less than 40%, we can either move some applications from our machine to another machine if we are running other applications apart from SQL Server or we can change the current disk system with a new and faster disk system.

The disk performance is:

Excellent, if the value of this counter is greater than 60% of total disk capacity.
Good, if the value of this counter is greater than 50% of total disk capacity.
Poor, if the value is constantly less than 40% of total disk capacity.

[Need assistance? We are happy to help you]

Conclusion

To conclude we saw how to use Perfmon Counters for disk usage. Also, we saw some commonly used performance counters which our Support Engineers use to identify SQL server disk bottlenecks.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

2 Comments

  1. diego

    thanks! from Argentine

    Reply
    • Maheen Aboobakkar

      You are welcome Diego.

      Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF