Home » RDBMS Server » Server Administration » Wait Class - DB CPU (12c)
Wait Class - DB CPU [message #637401] Sun, 17 May 2015 02:55 Go to next message
karthik4u
Messages: 36
Registered: September 2006
Location: CHENNAI
Member
We have collected AWR report during huge process which runs for nearly 4 hrs and in 30 parallel sessions.

From AWR report found that DB CPU wait class as follow

Wait Classes by Total Wait Time:

----
Wait Class Waits Total Wait Time (sec) Avg Wait (ms) % DB time Avg Active Sessions
DB CPU 107,579 63.8 6.0
----

How to reduce this Total Wait Time? What we need to check for the same in AWR report?

Kindly advice.
Re: Wait Class - DB CPU [message #637402 is a reply to message #637401] Sun, 17 May 2015 02:58 Go to previous messageGo to next message
karthik4u
Messages: 36
Registered: September 2006
Location: CHENNAI
Member
Wait Classes by Total Wait Time:

----
Wait Class---Waits---Total Wait Time (sec)----Avg Wait (ms)----% DB time----Avg Active Sessions
DB CPU------- ---107,579------------------ ---- 63.8--------6.0
----
Re: Wait Class - DB CPU [message #637403 is a reply to message #637402] Sun, 17 May 2015 03:50 Go to previous messageGo to next message
Michel Cadot
Messages: 65849
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

DB CPU is ot a real wait class, it is the time you spent on CPU that is actually working.
If you want to reduce it then reduce the work you ask the database to do.

Re: Wait Class - DB CPU [message #637427 is a reply to message #637402] Sun, 17 May 2015 09:06 Go to previous messageGo to next message
John Watson
Messages: 7622
Registered: January 2010
Location: Global Village
Senior Member
63.8% is not bad for CPU time. I would be nice to get it a bit higher, if you think that there is a problem. But you do have to define the problem. I do not think that any of your users have telephoned you to complain that "DB CPU wait class percentage is bad". What are they complaining about?
Re: Wait Class - DB CPU [message #637459 is a reply to message #637401] Mon, 18 May 2015 09:08 Go to previous messageGo to next message
bpeasland
Messages: 51
Registered: February 2015
Location: United States
Member

Your SQL statement's runtime is the sum of the time on the CPU and the sum of the total wait time. Many people focus on the wait time end of the equation. But I've seen many SQL statements that have a lot of CPU time and very little wait time.

Remember that there are two types of I/O, physical and logical. Physical I/O will show up as different wait events. Logical I/O will show up as CPU cycles. Reduce the logical I/O and the CPU consumption will go down. I often see this when a query is showing a very high number of logical reads, for example, the query is performing too many full table scans that the tables involved are all in the Buffer Cache.

Cheers,
Brian
Re: Wait Class - DB CPU [message #637460 is a reply to message #637401] Mon, 18 May 2015 09:22 Go to previous messageGo to next message
BlackSwan
Messages: 26207
Registered: January 2009
Location: SoCal
Senior Member
>We have collected AWR report during huge process which runs for nearly 4 hrs and in 30 parallel sessions.

How was 30 parallel session deemed as optimal?
Why not a higher or lower number?

How many CPU/core exist in the server system?
Re: Wait Class - DB CPU [message #637463 is a reply to message #637401] Mon, 18 May 2015 10:15 Go to previous message
Lalit Kumar B
Messages: 3131
Registered: May 2013
Location: World Wide on the Web
Senior Member
karthik4u wrote on Sun, 17 May 2015 13:25
30 parallel sessions.


30 parallel sessions? Seriously?

I mean for 30 parallel sessions, you need to have a big time hardware and infrastructure. Have a look at this and this.

[Updated on: Mon, 18 May 2015 10:21]

Report message to a moderator

Previous Topic: upgrade multiple databases of same oracle home from 11.2.0.1 to 11.2.0.3
Next Topic: Oracle Sizing
Goto Forum:
  


Current Time: Mon Oct 22 11:06:34 CDT 2018