测试了非工作量模式下Oracle11gR2全表扫描的成本计算,现在测试一下在工作量模式下Oracle11gR2全表扫描的成本计算 首先讲表blocks增加到10003个SQL> select owner,blocks from dba_tables where table_name="TEST" and owner="TEST";OWNER BLOCKS
------------------------------ ----------
TEST 10003然后人工设置工作量的CPUSPEED=2500,单块读等于5,多块读等于30,MBRC等于12SQL> begin
dbms_stats.set_system_stats("CPUSPEED",2500);
dbms_stats.set_system_stats("SREADTIM",5);
dbms_stats.set_system_stats("MREADTIM",30);
dbms_stats.set_system_stats("MBRC",12);
end;
/ 2 3 4 5 6 7PL/SQL procedure successfully completed.利用explain plan得到CPU_COST---这里等于 72735764SQL> explain plan for select count(*) from test;Explained.SQL> select cpu_cost from plan_table; CPU_COST
----------
72735764成本计算公式如下:Cost = (
#SRds * sreadtim +
#MRds * mreadtim +
CPUCycles / cpuspeed /1000
) / sreadtime
#SRds - number of single block reads
#MRds - number of multi block reads
#CPUCyles - number of CPU cyclessreadtim - single block read time
mreadtim - multi block read time
cpuspeed - CPU cycles per secondCost = (
#SRds * sreadtim + ---SRds=0
#MRds * mreadtim + ---MRds=BLOCKS/MBCR=10003/12, mreadtim=30
CPUCycles / cpuspeed / 1000 ---CPUCycles=PLAN_TABLE.CPU_COST,cpuspeed=2500
) / sreadtime
所以人工计算的成本等于:SQL> select ceil(10003/12*30/5)+ceil(72735764/2500/5/1000)+1 from dual;CEIL(10003/12*30/5)+CEIL(72735764/2500/5/1000)+1
------------------------------------------------
5009SQL> set autot trace
SQL> select count(*) from test;Execution Plan
----------------------------------------------------------
Plan hash value: 1950795681-------------------------------------------------------------------
| Id | Operation | Name | Rows | Cost (%CPU)| Time |
-------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1 | 5009 (1)| 00:00:26 |
| 1 | SORT AGGREGATE | | 1 | | |
| 2 | TABLE ACCESS FULL| TEST | 10000 | 5009 (1)| 00:00:26 |
-------------------------------------------------------------------人工计算的cost正好等于Oracle计算的Cost 这里也说明Oracle11gR2 在工作量模式下,www.linuxidc.com全表扫描的成本计算方法依然同Oracle9i,Oracle10g工作量模式下,从全表扫描的成本可以看出,参数db_file_multiblock_read_count 的更改对全表扫描成本计算没有影响,有影响的是MBRC,举个例子:SQL> show parameter db_file_multiblock_read_countNAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_file_multiblock_read_count integer 16
SQL> set autot trace
SQL> select count(*) from test;
Execution Plan
----------------------------------------------------------
Plan hash value: 1950795681-------------------------------------------------------------------
| Id | Operation | Name | Rows | Cost (%CPU)| Time |
-------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1 | 5009 (1)| 00:00:26 |
| 1 | SORT AGGREGATE | | 1 | | |
| 2 | TABLE ACCESS FULL| TEST | 10000 | 5009 (1)| 00:00:26 |
-------------------------------------------------------------------
SQL> alter session set db_file_multiblock_read_count=32;Session altered.SQL> select count(*) from test;
Execution Plan
----------------------------------------------------------
Plan hash value: 1950795681-------------------------------------------------------------------
| Id | Operation | Name | Rows | Cost (%CPU)| Time |
-------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1 | 5009 (1)| 00:00:26 |
| 1 | SORT AGGREGATE | | 1 | | |
| 2 | TABLE ACCESS FULL| TEST | 10000 | 5009 (1)| 00:00:26 |
-------------------------------------------------------------------
可以看到更改db_file_multiblock_read_count对于成本没有任何影响,因为工作量模式下的COST只跟MBRC有关。相关链接 http://www.linuxidc.com/Linux/2011-07/38576.htmUbuntu 11.04中 Oracle定时备份Oracle 11g R2 全表扫描成本计算(非工作量模式-noworkload)相关资讯 Oracle教程
- Oracle中纯数字的varchar2类型和 (07/29/2015 07:20:43)
- Oracle教程:Oracle中查看DBLink密 (07/29/2015 07:16:55)
- [Oracle] SQL*Loader 详细使用教程 (08/11/2013 21:30:36)
| - Oracle教程:Oracle中kill死锁进程 (07/29/2015 07:18:28)
- Oracle教程:ORA-25153 临时表空间 (07/29/2015 07:13:37)
- Oracle教程之管理安全和资源 (04/08/2013 11:39:32)
|
本文评论 查看全部评论 (0)