|
|
如果数据库版本是9.2,The Top 5 Wait Events变为Top 5 Timed Events.
o The Top 5 Wait Events has been changed to be the Top 5 Timed Events.
What was previously the Top 5 Wait Events has been expanded to give the
Top 5 time usage within the instance: i.e. in addition to including Wait
events, this section can now include the 'CPU used by this session'
statistic. This statistic will appear in the Top 5 only if it's value
is one of the the Top 5 users of time for the snapshot interval.
Note that the name of the statistic 'CPU used by this session' will
actually appear in the Top 5 section as 'CPU Time'. The statistic
name is masked in the Top 5 to avoid the confusion of the suffix
'by this session'.
The statistic will continue to appear in the System Statistics
(SYSSTAT) section of the report as 'CPU used by this session'.
Additionally, instead of the percentage calculation being the % Total
Wait Time (which is time for each wait event divided by the total wait
time for this snapshot interval), the percentage calculation is now
% Total Elapsed Time (which is time for each timed event divided by
the total elapsed time).
i.e.
previously: time for each wait event / total wait time for all events
now: time for each timed event / total elapsed time
The total elapsed time is computed using the total wait time for all
events added to the total CPU time used for the interval
i.e.
total elapsed time = total wait time + total CPU time
Purpose
~~~~~~~
The purpose for including CPU time with wait events:
When tuning a system, the first step is to identify where the most of the
time is spent, in order to identify where the most productive tuning
effort should be concentrated.
The majority of time could be spent in waiting for events to complete
(and so be identifyable in the wait event data), or the system could be
consuming much CPU (for which Operating System statistics, and the Oracle
CPU statistic 'CPU used by this session' in SYSSTAT are examined).
Having the CPU Time co-located with the wait events in the Top 5 section
of the instance report makes it easier to compare the relative values
and to identify whether the most productive investigation would occur
by drilling down the wait events, or in reducing Oracle CPU usage
(e.g. by tuning SQL).
可以参考oracle自带的statspack文档:
%ORACLE_HOME%\rdbms\admin\statspack.doc |
|