You were brought to this page based on an internet search
and as a free service to Oracle DBAs.
The text below is an except from the book,
Oracle Performance Firefighting, written by
Craig Shallahamer of
OraPub, Inc.
Figures and tables are not included on this page, only their reference.
To order the book in either print or PDF form, click
here.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
-------------------------------
In summary, to determine the average CPU utilization, some tools you can use are vmstat, sar, /proc/stat, and even v$osstat. So, if you don't have the operating system privileges you need, starting with Oracle Database 10g, you can still calculate the utilization.
The CPU run queue is key to understanding the health of your CPU subsystem. Combined with the average utilization, it gives you everything you need to tell if there is a CPU bottleneck.
While it seems strange, the run queue reported by the operating system includes processes waiting to be serviced by a CPU as well as processes currently being serviced by a CPU. This is why you may have heard it's OK to have a run queue up to the number of CPUs or CPU cores. As discussed earlier, for an OLTP-centric system, we do not want processes waiting to be serviced, so we do not want the run queue to be greater than the number of CPU cores.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
|