Oracle AWR報告及統計資料之DB Time說明
轉自:
在Oracle Database 10g中引入了DB time指標,其實這並不算是新概念。
先摘錄一些官方的說明(Oracle Database Performance Tuning Guide 10g Release 2 (10.2) B14211-01)
DB Time
總結出來就是db time= cpu time + wait time(不包含空閒等待) (非後臺程式)
說白了就是db time就是記錄的伺服器花在資料庫運算(非後臺程式)和等待(非空閒等待)上的時間
列出下面這兩個來做解釋:
伺服器是AIX的系統,4個雙核cpu,共8個核:
cpu花費了466.37分鐘在處理Oralce非空閒等待和運算上(比方邏輯讀)
也就是說cpu有 466.37/480*100% 花費在處理Oracle的操作上,這還不包括後臺程式
看Report B,總共約60分鐘,cpu有 19.49/480*100% 花費在處理Oracle的操作上
很顯然,2中伺服器的平均負載很低。
從awr report的Elapsed time和DB Time就能大概瞭解db的負載
在Oracle Database 10g中引入了DB time指標,其實這並不算是新概念。
先摘錄一些官方的說明(Oracle Database Performance Tuning Guide 10g Release 2 (10.2) B14211-01)
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.
/*記住:如果只有一個cpu,就不可能4個session同時處於no-idle,所以下面這個假設只能在大於4cpu的伺服器上成立。
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.
*/
By reducing DB time, the database server is able to support more user requests using the same resources, which increases throughput.
總結出來就是db time= cpu time + wait time(不包含空閒等待) (非後臺程式)
說白了就是db time就是記錄的伺服器花在資料庫運算(非後臺程式)和等待(非空閒等待)上的時間
列出下面這兩個來做解釋:
Report A:
Snap Id Snap Time Sessions Curs/Sess
--------- ------------------- -------- ---------
Begin Snap: 4610 24-Jul-08 22:00:54 68 19.1
End Snap: 4612 24-Jul-08 23:00:25 17 1.7
Elapsed: 59.51 (mins)
DB Time: 466.37 (mins)
Report B:
Snap Id Snap Time Sessions Curs/Sess
--------- ------------------- -------- ---------
Begin Snap: 3098 13-Nov-07 21:00:37 39 13.6
End Snap: 3102 13-Nov-07 22:00:15 40 16.4
Elapsed: 59.63 (mins)
DB Time: 19.49 (mins)
伺服器是AIX的系統,4個雙核cpu,共8個核:
/sbin> bindprocessor -q先說Report A,在snapshot間隔中,總共約60分鐘,cpu就共有60*8=480分鐘,DB time為466.37分鐘,則:
The available processors are: 0 1 2 3 4 5 6 7
cpu花費了466.37分鐘在處理Oralce非空閒等待和運算上(比方邏輯讀)
也就是說cpu有 466.37/480*100% 花費在處理Oracle的操作上,這還不包括後臺程式
看Report B,總共約60分鐘,cpu有 19.49/480*100% 花費在處理Oracle的操作上
很顯然,2中伺服器的平均負載很低。
從awr report的Elapsed time和DB Time就能大概瞭解db的負載
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/90618/viewspace-609699/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- oracle特性之AWR報告2Oracle
- 獲取Oracle資料庫awr報告方法Oracle資料庫
- Oracle AWR報告分析之–SQL ordered byOracleSQL
- 【AWR】Oracle資料庫匯出效能報告幾個指令碼的小說明Oracle資料庫指令碼
- Oracle生成awr報告Oracle
- Oracle 生成awr報告Oracle
- oracle效能awr報告Oracle
- 【AWR】Oracle批量生成awr報告指令碼Oracle指令碼
- Oracle AWR 介紹及報告分析(2) finalOracle
- Oracle AWR 介紹及報告分析(1) finalOracle
- Oracle AWR報告大綱Oracle
- oracle 產生awr 報告Oracle
- oracle AWR報告提取分析Oracle
- Oracle RAC CSS 超時計算及引數 misscount,Disktimeout 說明 .OracleCSS
- MySQLReport 報告說明MySql
- Statspack分析報告說明
- Oracle AWR(Automatic Workload Repository) 說明Oracle
- ORACLE AWR報告詳細分析Oracle
- 用Excel做資料說明――描述統計Excel
- Oracle AWR報告詳細解讀Oracle
- ORACLE 11G生成AWR報告Oracle
- Oracle 10g AWR 報告分析Oracle 10g
- Oracle TIMED_STATISTICS 引數 說明Oracle
- 舉例說明Oracle資料庫審計的用法Oracle資料庫
- oracle資料塊轉儲說明Oracle
- 轉載詳細的Oracle ASH/AWR介紹及報告分析Oracle
- ORACLE AWR效能報告和ASH效能報告的解讀Oracle
- 本機生成遠端資料庫AWR報告資料庫
- HSQL DB 使用說明SQL
- Oracle AWR與ASH效能報告深入解析Oracle
- Oracle 11g 手工跑AWR報告Oracle
- Oracle11.2新增GLOBAL AWR報告Oracle
- oracle 10g awr報告的收集Oracle 10g
- Oracle的AWR報告分析(簡潔版)Oracle
- 基於AWR實現STATSPACK報告(3-RAC統計)
- 達夢資料庫AWR報告日常管理方法資料庫
- Oracle Audit 審計 說明Oracle
- AWR報告分析之一:高 DB CPU 消耗的效能根源-eygle