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.
-------------------------------
Figure 9-2. Two other Statspack sections from the report in Figure 9-1. The timing detail and a few of the statistics in the Instance Statistics sections are shown. This is enough information to calculate the workload; that is, the arrival rate expressed in commits, transactions, logical IOs, and user calls per second.
Using the data shown in Figure 9-2, the user calls per second workload metric is calculated as follows:
Referencing the Load Profile's user calls per second metric shown in Figure 9-1, notice it closely matches our calculation of 414.84 uc/s. The difference is due to the two-digit precision of 149.97 minutes. Knowing that an Oracle transaction contains both commits (statistic user commits) and rollbacks (statistic user rollbacks), you can calculate the transaction rate and compare that to the load profile. You'll find the Statspack report does the math correctly.
©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.
|