So I know what wait times are, the amount of time SQL spends waiting on a resource. What I don't understand is how this equates to end user wait time and how the numbers can be so high.
Take for example my companies total disk wait stats for 2012: 249,440,577,575ms or 7.9 years! I know there are multiple processes that can wait at the same time but 7.9 years of waiting seems crazy. My average disk read latency for last year was 3.6ms and write latency was 3.8ms so I don't think I have a disk issue.
Here is another example: in the past day my total disk resource waits are 11,252,662ms or 3.1 hours. Nothing seems to be hanging up and I am not getting any reports of the system being slow. The total CLR waits for the same time period are 30,302,950,440ms. I know Microsoft says you can safely ignore CLR waits but a number that large I have a hard time ignoring.
Could it be that I am just looking at waits that are okay to ignore and my actual wait time is not that high? Hopefully someone here can help, I'm lost at trying to explain it.