Originally Posted by
PAVB
Please run query below, then post results in between code tags.
So I ran the query against one of my databases that has had performance issues, and it looks like a statspack report. I was wondering what specific things do you suggest people look at in order to diagnose performance problems? Do the following two stats tell me that I am doing too many full tablescans?
Code:
db file scattered read 33,168,651 478,165 0 .014
db file sequential read 69,640,302 407,351 0 .006
Do you spool to a file and grep for the word contention or the word wait? If I see that the longest average wait is less than 4 seconds, what does that really mean? I thought tuning by ratios was for the most part debunked. 
Reply With Quote