Re: optimizer_index_cost_adj and optimizer_index_caching
- From: "Jonathan Lewis" <jonathan@xxxxxxxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Sat, 6 Mar 2004 07:19:01 -0000
Notes in-line
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
March 2004 Hotsos Symposium - The Burden of Proof
Dynamic Sampling - an investigation
March 2004 Charlotte OUG (www.cltoug.org) CBO Tutorial
April 2004 Iceland
June 2004 UK - Optimising Oracle Seminar
----- Original Message -----
From: "Wolfgang Breitling" <breitliw@xxxxxxxxxxxxx>
: That is how I interpret it too, which is why I prefer using system_stats
: over changing o_i_c_a. There is a subtle difference between the way
o_i_c_a
: and system_stats achieve the apparently same goal:
: o_i_c_a lowers the cost of index accesses compared to the
baseline
: whereas
: system_stats increase the cost of full scans compared to the
baseline
Very good point
:
: I have not figured out yet if that can lead to differences in plan
: compositions or if it is guaranteed that the relative costs of all plan
: components remain the same when comparing a plan stemming from having
: o_i_c_a=25 (i.e. single reads cost are 1/4 of multi read costs) vs. having
: system statistics where mreadtim = 4*sreadtim.
:
In theory it might - It would depend
on how Oracle handles the the "plus 1"
for tablescans in the new calculation.
----------------------------------------------------------------
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 http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
- Follow-Ups:
- Re: optimizer_index_cost_adj and optimizer_index_caching
- From: Wolfgang Breitling
- References:
- RE: optimizer_index_cost_adj and optimizer_index_caching
- From: Niall Litchfield
- RE: optimizer_index_cost_adj and optimizer_index_caching
- From: Wolfgang Breitling
- Re: optimizer_index_cost_adj and optimizer_index_caching
- From: Jonathan Lewis
- Re: optimizer_index_cost_adj and optimizer_index_caching
- From: Wolfgang Breitling
Other related posts:
- » optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » RE: optimizer_index_cost_adj and optimizer_index_caching
- » RE: optimizer_index_cost_adj and optimizer_index_caching
- » RE: optimizer_index_cost_adj and optimizer_index_caching
- » RE: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » RE: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- » RE: optimizer_index_cost_adj and optimizer_index_caching
- » Re: optimizer_index_cost_adj and optimizer_index_caching
- Re: optimizer_index_cost_adj and optimizer_index_caching
- From: Wolfgang Breitling
- RE: optimizer_index_cost_adj and optimizer_index_caching
- From: Niall Litchfield
- RE: optimizer_index_cost_adj and optimizer_index_caching
- From: Wolfgang Breitling
- Re: optimizer_index_cost_adj and optimizer_index_caching
- From: Jonathan Lewis
- Re: optimizer_index_cost_adj and optimizer_index_caching
- From: Wolfgang Breitling