Trouble-shooting with Statspack / AWR:
Something has to be top of the “Top 5 Timed Waits” … even when there are no performance problems.
Trouble-shooting with Statspack / AWR:
Something has to be top of the “Top 5 Timed Waits” … even when there are no performance problems.
RSS feed for comments on this post.
Theme: Rubric. Blog at WordPress.com.
I like the mantra “If no one is complaining, there are no performance problems”…….
Comment by Craig T — September 10, 2009 @ 7:30 pm UTC Sep 10,2009 |
Said by me when the system I had been setting up went into production: “The system ran fine without anyone on it!”
Comment by Gary E — September 10, 2009 @ 8:08 pm UTC Sep 10,2009 |
Just shutdown the listener and keep it that way :D
Comment by Daniel Stolf — September 11, 2009 @ 2:21 pm UTC Sep 11,2009 |
When your own scripts for checking performance are the most demanding statements in the system, either your job is done or you need to tune your own scripts :-)
(sheepishly once guilty of the second situation)
Comment by randolfpant — September 10, 2009 @ 9:49 pm UTC Sep 10,2009 |
I’ve found Foglight monitoring SQL at the top of the pile before – so wind down the sampling from every couple of secs to every 30 minutes
Comment by Nigel Thomas — September 11, 2009 @ 10:21 am UTC Sep 11,2009 |
…and if you do not recognise this, you will develop Compulsive Tuning Disorder!
Comment by David Kurtz — September 11, 2009 @ 11:39 am UTC Sep 11,2009 |
If no one is complaining, either the lead pipe is working or the phone is down.
Comment by joel garry — September 11, 2009 @ 10:05 pm UTC Sep 11,2009 |
Or as the pessimist might say in the light of this comment: no-one’s complaining because they’ve given up hope.
Comment by Jonathan Lewis — September 11, 2009 @ 10:12 pm UTC Sep 11,2009 |
Don’t get me started on how much time I wasted explaining to a local “expert” that redo log write waits of less than 1ms in 99% of the cases is NOT a performance problem…
Comment by Noons — October 10, 2010 @ 9:20 pm UTC Oct 10,2010 |
Something has to be top of the “Top 5 Timed Foreground Events” (11gR2 AWR)
Comment by Jayant — January 12, 2012 @ 11:13 pm UTC Jan 12,2012 |