I am using ignite DPA for past 3 days for monitoring a sqlserver 2008 R2 which hasnt been rebooted in an year. Application seems to be running slow for the past few days and I am currently looking at the perf metrics like
sql disk read latency, sql disk write latency, sql compilations per sec and sql recomiplations per sec.
Per ignite the avg sql disk read latency is shown as 90 ms,
avg sql disk write latency as 140ms ,
avg sql compilations per sec as 300
avg sql recomiplations per sec as 35.
Can these be taken into consideration for improving performance or do you think the server needs to be rebooted before monitoring using DPA?
There should be no relationship between reboots and the collected metrics. If you say the application is running slowly and are seeing disk latency in the 90-140 ms range then you basically already have identified an issue. I normally expect my systems to have latencies under 20 ms, but obviously each company sets their own standards for what "fast enough" means to them.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.