AWR 报告的解读

[复制链接]
查看11 | 回复2 | 2007-10-20 08:38:44 | 显示全部楼层 |阅读模式
Snap IdSnap TimeSessions Curs/Sess

--------- ------------------- -------- ---------
Begin Snap: 33128 28-Apr-09 10:00:2018 #########
End Snap: 33129 28-Apr-09 11:00:1618 #########
Elapsed:
59.93 (mins)
DB Time:
117.32 (mins)

为什么ELAPSED 1小时, 而DB TIME 是2小时啊?

Time% Total
Statistic Name
(seconds) DB Time
--------------------------------------------- -------------- -----------
sql execute elapsed time
7,046.36100.10
PL/SQL execution elapsed time
7,042.28100.05
DB time
7,039.04100.00
回复

使用道具 举报

千问 | 2007-10-20 08:38:44 | 显示全部楼层
2个CPU?
回复

使用道具 举报

千问 | 2007-10-20 08:38:44 | 显示全部楼层
DB Time
Amount of elapsed time (in microseconds) spent performing Database user-level calls. This does not include the time spent on instance background processes such as PMON.
The most important of the time model statistics is DB time. This statistics represents the total time spent in database calls and is a indicator of the total instance workload. It is calculated by aggregating the CPU and wait times of all sessions not waiting on idle wait events (non-idle user sessions). DB time is measured cumulatively from the time that the instance was started.
Because DB time it is calculated by combining the times from all non-idle user sessions, it is possible that the DB time can exceed the actual time elapsed since the instance started up. For example, a instance that has been running for 30 minutes could have four active user sessions whose cumulative DB time is approximately 120 minutes.

db time就是记录的服务器花在数据库运算(非后台进程)和等待(非空闲等待)上的时间
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

主题

0

回帖

4882万

积分

论坛元老

Rank: 8Rank: 8

积分
48824836
热门排行