Hi @sakuraime ,
A high Avg. Disk sec/Write and Avg. Disk sec/Read performance counter value may occur due to a burst of disk write and read requests by either an operating system or application. In general, for the performance counter value of Avg. Disk sec/Write and Avg. Disk sec/Read, under 10ms is good. 10-20ms is average. Over 50ms is bad.
For both Current and Avg. Disk Queue Length, the higher the number the more disk operations are waiting. It requires attention if this value frequently exceeds a value of 2 during peak usage of SQL Server. If you have multiple drives you should take this number and divide by the number of drives in the array to see if the number is above 2. For example, you have 4 drives and a disk queue length of 10, this would be 2.5(10/4 ). 5 or more requests per disk could suggest that the disk subsystem is bottlenecked.
Please refer to How to Identify IO Bottlenecks in MS SQL Server and Current & Average Disk Queue Length Counter for more details.
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.