Edgar, I don't doubt we need to care about LIO from concurrency/scalability point of view. But for CPU utilization we can?t use LIOs statistics. Jurijs Edgar Chupit <edgars.cupits@xxxxx> 29.06.2004 23:55 Please respond to Edgar Chupit To: J.Velikanovs@xxxxxxxx cc: oracle-l@xxxxxxxxxxxxx Subject: Re: How to compare two different SQL executions plans (question is more deeper then seams from first look)? Hello Jurijs, JVal> Fastest from two SQL (or SQL execution plans) will be SQL with lower LIO JVal> indicator. We still have to remember about "scalability" (latches/locks), correct me if I'm wrong, but you still have to chose statement with lowest lio, because even if the cpu_usage is the same as with statement with larger lio count, the statement with smaller lio count will scale better. You can use package similar to T.Kytes run_stats or directly query v$mystat to see other meaningful characteristics. I guess rule to minimize lio count can still apply, however as we all know, there is no golden rules that apply to all possible cases. -- Best regards, Edgar mailto:edgars.cupits@xxxxx ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------