| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Performance monitoring
Very well said.
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Upcoming events:
- Hotsos Clinic, Oct 1-3 San Francisco, Oct 15-17 Dallas, Dec 9-11
Honolulu
- 2003 Hotsos Symposium on OracleR System Performance, Feb 9-12 Dallas
- Jonathan Lewis' Optimising Oracle, Nov 19-21 Dallas
-----Original Message-----
Sent: Wednesday, October 02, 2002 4:18 PM
To: Multiple recipients of list ORACLE-L
The ten most important performance items to monitor are your ten most important business transactions. Period, end of story.
If you want to provide an intelligent response, monitor how long they
take
and provide a weekly report, noting any changes.
Ratios and wait events are just diagnostic tools -- when business transactions become slow you use them to find where the problem is.
Anyone who asks you to monitor ten internal things, such as ratios or
wait
events, and no more than just ten because they only want the ten most
important, is simply uneducated and unexperienced, since these things
are of
no importantance if the system is running fast enough for the users, and
besides there are way more than ten important things like this.
However,
they may also be very smart, since a good manager may be wise to start
by
getting a handle on the ten most important things.
Probably, you want to be taking statspack snapshots every hour just to
have
a baseline, so just DO THAT and give the statspack report to the manager
once a week -- and make them happy by picking out ten items you consider
important and running a yellow highlighter over them. Have a cover page
that compares the current value of the ten items with the same items
four
weeks ago -- so you are monitoring them. That's fast, easy and smart,
it
makes your manager happy and you'll have your eye on the ball too.
But don't forget that the most important thing to monitor is reality.
Your
coolest move is to have the manager pull the users into a meeting and
get
them to identify the ten business transactions that are most important
to
them. Find out if any are too slow. Find out if anything is too slow.
Monitor that. Tune that.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Greg Moore
INET: sqlgreg_at_pacbell.net
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services ---------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Cary Millsap
INET: cary.millsap_at_hotsos.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services ---------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Wed Oct 02 2002 - 18:48:20 CDT
 |
 |