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.
-------------------------------
Continuing with our example, Figure 9-2 shows the sample interval to be 149.97 minutes in which the logical IO value (sum of db block gets and consistent gets) is 1,307,632,010. Here is the arrival rate math:
Based on Figure 9-3, the total service time is 16,881.6 seconds, or 16,881,600 milliseconds. Determine the service time by dividing the total service time by the unit of work value. Here is the service time math:
Determine the queue time by dividing the total queue time by the unit of work value. For Oracle systems, the total queue is all the non-idle wait time that occurred during the sample interval. Most Statspack and AWR reports have a Top 5 Timed Events section near the top of their reports. This is simply the top four most time-consuming wait events and also the CPU time. Usually the top four wait events account for 90% or more of all the non-idle wait time. For our required level of precision, we can simply sum the wait time for the top four wait events. While the details are not shown, their combined wait time is 45,672 seconds during the sample interval. Here is the queue time math:
©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.
|