|
|
by Craig Shallahamer Get the book here |
|
|
Craig Shallahamer's Blog
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. Please—Out 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. ------------------------------- * Average user call activity was 1,510 uc/sec; that is, 5,400,000 user calls occurred in the one-hour time span. This will be the arrival rate (the workload). * CBC latch contention accounted for 90% of the total wait time; that is, 28,920 seconds. So nearly all of the wait time (queue time) is related to CBC latch contention. * Oracle consumed 93% of the available database server CPU capacity, which contains 12 CPU cores. Utilization is simply consumption divided by capacity. The total CPU capacity equals the interval duration (60 minutes) multiplied by the 12 CPU cores; that is, 720 minutes, or 43,200 seconds. Said another way, within any one-hour period, a 12 CPU core server can provide up to 720 minutes of CPU power. Statspack showed Oracle CPU consumption was 39,960 seconds. Therefore, Oracle used 39,960 seconds of the available 43,200 seconds of CPU, which is 93%.15 Please—Out 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. |
Know what's important before it's too late!
OraPub's
Performance Training
is like no other...
More Class Pics...
Get student testimonials!