RE: cpu average load
- From: <Paula_Stankus@xxxxxxxxxxxxxxx>
- To: <gogala@xxxxxxxxxxxxx>
- Date: Sun, 5 Dec 2004 06:53:14 -0500
Thanks Mladen,
Well put. Again, I am not trying to look for problems where there are
not. I simply don't have time for that. However, my management has
insisted on this type of monitoring then when they get "reports" they
come and ask me to explain what is happening. I am not sure they will
accept the explanation you have below but you have definitely given me
some ideas.
Thanks,
Paula=20
-----Original Message-----
From: Mladen Gogala [mailto:gogala@xxxxxxxxxxxxx]=20
Sent: Friday, December 03, 2004 11:37 PM
To: Stankus, Paula G
Cc: oracle-l
Subject: Re: cpu average load
On 12/03/2004 11:05:28 PM, Paula_Stankus@xxxxxxxxxxxxxxx wrote:
> (as a whole) then drilling down from there. Also, proactively=20
> monitoring system resource utilization on a regular basis if you are=20
> supporting a number of databases operationally has proven useful to=20
> me.
There is a good carpentry book about some wooden tables and some other
forms of furniture in which one among the authors mentions an old IBM
criteria: job that consumes more then 8 CPU seconds is considered a
batch. I believe that the similar criteria can apply today:
If you have dedicated server configuration and if any of the server
processes on an OLTP system has accumulated more then 8 seconds of CPU
is considered a candidate for an investigation. In the days of yore IBM
didn't use the 8 CPU seconds criteria as an indicator, they used as a
criteria to separate batch, OLTP and DW. That philosophy is still
relevant today.
The illusion of proactive monitoring revealing you a problem is just
snake oil. You cannot monitor perception and it is user's perception of
the application that counts. You can only monitor consumption of
computer resources: CPU, memory, I/O bandwidth, semaphores and network
bandwidth. The fact that some process resource consumption is above a
chosen mark does not mean that the process should not do it or that you
have a problem with the resources. Tuning is always reactive, because in
order to start tuning, something must be out of the tune.
Resource consumption alone can not tell you that. Sometimes a form made
with a disregard for the rules of good UI design can make users unhappy
and nagging about the "database being slow", and a simple redesign and
adding a select list and rearranging fields on the screen so that
logically grouped information is visually close can make users stop
complaining. May be Pythias would be able to predict that, after all,
her predictions where said quixotically on laurel (SQL for short) but I
am not. Any regular report you give to your management is exclusively
for their own amusement and is, generally speaking, useless as a health
indicator.
--
Mladen Gogala
Oracle DBA
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
Teach CanIt if this mail (ID 17576167) is spam:
Spam:
https://dohsmsi01.doh.state.fl.us/canit/b.php?c=3Ds&i=3D17576167&m=3D699d=
2a0e9
8ce
Not spam:
https://dohsmsi01.doh.state.fl.us/canit/b.php?c=3Dn&i=3D17576167&m=3D699d=
2a0e9
8ce
Forget vote:
https://dohsmsi01.doh.state.fl.us/canit/b.php?c=3Df&i=3D17576167&m=3D699d=
2a0e9
8ce
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS
--
//www.freelists.org/webpage/oracle-l
Other related posts:
