Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Tim Gorman's "...Cost-Based Optimizer.doc"

RE: Tim Gorman's "...Cost-Based Optimizer.doc"

From: Khemmanivanh, Somckit <somckit.khemmanivanh_at_weyerhaeuser.com>
Date: Thu, 16 Jun 2005 10:36:02 -0700
Message-ID: <65C0D8935651CB4D96E97CEFAC5A12B9444674@wafedixm10.corp.weyer.pri>


Could it be that scattered reads take less time "if" the next block of data to be read is "actually" adjacent to the last block read, therefore you wouldn't be incurring seek time as you might with sequential reads?=20

Thanks!=20
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Marquez, Chris Sent: Thursday, June 16, 2005 7:53 AM
To: mgogala_at_allegientsystems.com; oracle-l_at_freelists.org Subject: Tim Gorman's "...Cost-Based Optimizer.doc"

One comment / question on OPTIMIZER_INDEX_COST_ADJ; It seems that on "NON-cached" filesystems (e.g. RAW, OCFS) that there would/do NOT be a great difference in "db file scattered reads" vs. "db file sequential reads" AVERAGE_WAITS...as every read from disk (on non-cached filesystem) is a *real* read from dusk...no OS buffer to help, no?

Thanks,

Chris Marquez
Oracle DBA

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jun 16 2005 - 13:41:11 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US