You can see resmgr:cpu quantum ( resource_manager_cpu_allocation ) wait event in Performance page of Oracle Enterprise Manager Cloud Control 13c.
resmgr:cpu quantum ( resource_manager_cpu_allocation ) Wait Event
When I take AWR ( Automatic Workload Repository ) report, I saw that There are resmgr:cpu quantum Wait Event in AWR.
resource_manager_cpu_allocation
To solve this problem, I have changed resource_manager_plan and cpu_count parameters like following.
SQL> show parameter resource
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
resource_limit boolean TRUE
resource_manager_cpu_allocation integer 56
resource_manager_plan string SCHEDULER[0x444D]:DEFAULT_MAIN
TENANCE_PLAN
SQL>
SQL> alter system set resource_manager_plan='' scope=both sid='*';
System altered.
SQL>
SQL>
SQL> show parameter resource
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
resource_limit boolean TRUE
resource_manager_cpu_allocation integer 56
resource_manager_plan string
SQL>
SQL>
SQL> show parameter cpu
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
cpu_count integer 8
parallel_threads_per_cpu integer 2
resource_manager_cpu_allocation integer 56
SQL>
SQL>
SQL> alter system set cpu_count=32 scope=both sid='*';
System altered.
SQL> show parameter cpu
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
cpu_count integer 32
parallel_threads_per_cpu integer 2
resource_manager_cpu_allocation integer 56
SQL>
SQL>
cpu_count parameter
I have increased cpu_count parameters from 8 to 32 then Scheduler and resmgr:cpu quantum Wait Event are disappeared.
Does your system have 8 or 32 cpu? If you only have 8 how would that solve the problem? Wouldnt that stress the server?
it would stress the server, if CPU wait is always TOP, then you need to increase it.
Thanks for the fast reply. You mean increase CPU on the server?
yes
Hi Mehmet, high meaning what percentage?
about %10 or you already feel it from the database slowness.