Skip to Main Content

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Nikhil.

Asked: January 18, 2017 - 10:45 am UTC

Last updated: January 20, 2017 - 12:12 pm UTC

Version: 11.2.0.4.0

Viewed 1000+ times

You Asked

Hi Chris/Connor,

Could you please have a look at below -

AWR showing ~80% DB time was related to wait for CPU.

resmgr:cpu quantum 37,477,426 8706K 232 79.1 Scheduler

I was searching for resmgr in various forum, what i got in one of the blog is to disable resource manager -
http://dbakevin.blogspot.com/2012/11/resmgrcpu-quantum.html

Could you please help how to analysis this resmgr:cpu quantum section in AWR.


and Connor said...

"resmgr:cpu quantum" means the resource manager is doing exactly what is has been asked to do - control access to resources.

You see this event when the box is under strain to the extent that we need to be able to guarantee sufficient resources to whatever services you have defined as high priority. Other sessions that are consuming excessive resource (in this case CPU) are forced to 'sleep' aka 'resmgr:cpu quantum' so that critical services get a slice of the CPU.

Yes you could turn off resource manager by resetting 'resource_manager_plan', but all that means is that whatever session(s) are consuming all of your CPU now have no throttling applied, so they might stop other sessions from getting the resources they need.

I would like at *why* your box is under strain - tackle that first.

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

To share AWR

Nikhil Patil, January 19, 2017 - 12:26 pm UTC

Hi Connor,

Is there any way, where I can share snapshot of AWR?
Connor McDonald
January 20, 2017 - 12:12 pm UTC

A report ? or the raw data ?

You can email files to asktom_us@oracle.com

More to Explore

Performance

Get all the information about database performance in the Database Performance guide.