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.
-------------------------------
However, the scattered read wait time of 0.093 ms occurs much more frequently than the other waits. A more accurate average calculation would take into account the occurrences of the scattered read waits in addition to its average event wait time. This is called a weighted average, and it is a much better average calculation when working with diverse and highly variant data sets, as we have here.
The average calculation, weighted by the total wait time (which includes the weight occurrences) is shown in Figure 9-21. It is calculated as follows:
If you think about it, the weighted concept makes sense. Because the scattered read waits happen so much more often, the average IO read time should reflect this and be pulled toward the scattered read wait times. As Figure 9-21 shows, the weighted average value actually rounds to the average scattered read wait time of 0.093. While the difference may seem insignificant, not only can this have a dramatic effect when anticipating the impact of a performance solution, but it also makes the averages more realistic.
©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.
|