RE: Oracle Database Resource Manager
- From: Wolfson Larry - lwolfs <lawrence.wolfson@xxxxxxxxxx>
- To: "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 3 May 2004 16:17:19 -0500
Jonathan,
So are you still running DRM?
My databases are SUN 8.1.7.4 or 9.2.04 and HP-UX 8.1.7.4 or 9.2.0.4.
Thanks
Larry Wolfson
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Jonathan Lewis
Sent: Monday, May 03, 2004 3:49 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Oracle Database Resource Manager
Notes in-line.
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
Optimising Oracle Seminar
http://www.jlcomp.demon.co.uk/seminar.html
June 2004 UK Manchester
July 2004 Iceland
July 2004 USA California
Aug 2004 USA North Carolina
Sept 2004 UK Manchester
Sept 2004 USA NYC
Oct 2004 USA Boston
----- Original Message -----
From: "Pete Sharman" <peter.sharman@xxxxxxxxxx>
To: <oracle-l@xxxxxxxxxxxxx>
Cc: "Peter Ross Sharman" <PETER.SHARMAN@xxxxxxxxxx>
Sent: Monday, May 03, 2004 8:27 PM
Subject: RE: Oracle Database Resource Manager
I don't know who the instructor was, but he or she is talking crap (pardon =
my French). Really, what would be the point of implementing a resource man=
ager that itself takes too many resources?
[jl] Good question - I asked myself the same thing when
[jl] I first ran the 9.0.1 resource manager on my HP-UX
[jl] box. Under some conditions the overhead was about
[jl] 100%. Things improved when the sampling rate was
[jl] dropped somewhat.
One thing that people get confused about with the Resource Manager, BTW, is=
when it actually takes effect. It's when the resource being managed is ex=
hausted i.e. if you're allocating different amounts of the CPU utilization =
to different groups, you WON'T see Resource Manager kick in until CPU utili=
zation hits 100%. After all, it's not a problem till then, right?
[jl] I've found that it tends to kick in only after the demand
[jl] exceeds about 200% of available resources; and then
[jl] the allocation fractions aren't obeyed particularly well.
[jl] One of the positive things about it though is that you
[jl] can set it up to error out any SQL whose calculated
[jl] cost exceeds a given limit - which means less of the
[jl] 'query from hell' stuff wrecking performance for
[jl] everyone else on the system.
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
**********************************************************************
The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly
prohibited.
If you have received this communication in error,
please re-send this communication to the sender and
delete the original message or any copy of it from your
computer system. Thank You.
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
