first_rows(n)和all_rows在性能上的区别.docxVIP

在收集数据做另一个ppt的时候，需要first_rows(n)跟all_rows的一些对比数据，我直接把原数据整理了一下，大家有兴趣可以看下。最后有结论。。。——————————————————————————————实验分隔线———————————————————————————————————————create table t as select * from dba_objects;create table t1 as select * from t;create index ind_object_id on t(object_id) compute statistics;create index ind_t1_object_id on t1(object_id) compute statistics;analyze table t compute statistics for table for all columns;analyze table t1 compute statistics for table for all columns;准备好测试表和索引后来看看测试脚本all_rows模式:alter session set events’10053 trace name context forever,level 1′;alter session set optimizer_mode=all_rows;select t.owner from t,t1 where t.object_id = t1.object_id; alter session set events’10053 trace name context off’;first_rows_1模式:alter session set events’10053 trace name context forever,level 1′;alter session set optimizer_mode=first_rows_1;select t.owner from t,t1 where t.object_id = t1.object_id; alter session set events’10053 trace name context off’;first_rows_10模式:alter session set events’10053 trace name context forever,level 1′;alter session set optimizer_mode=first_rows_10;select t.owner from t,t1 where t.object_id = t1.object_id; alter session set events’10053 trace name context off’;first_rows_100模式:alter session set events’10053 trace name context forever,level 1′;alter session set optimizer_mode=first_rows_100;select t.owner from t,t1 where t.object_id = t1.object_id; alter session set events’10053 trace name context off’;由于篇幅太长,所以把10053的trace文件简化了一下,只留下join这一部分的内容,并把merge join的部分去除了测试环境是10g r2all_rows:**************************GENERAL PLANS**************************Considering cardinality-based initial join order.***********************Join order[1]: T[T]#0 T1[T1]#1***************Now joining: T1[T1]#1***************NL Join Outer table: Card: 51986.00 Cost: 164.59 Resp: 164.59 Degree: 1 Bytes: 9 Inner table: T1 Alias: T1 Access Path: TableScan NL Join: Cost: 8493121.71 Resp: 8493121.71 Degree: 0 Cost_io: 8358538.00 Cost_cpu