Mladen Gogala apparently said,on my timestamp of 21/06/2004 3:50 PM:
> Well, that is not quite true. If there are big tables that need to be read by using
> full table scan, than 16k buffer pool can act as recycle buffer pool and those
> big tables will be read faster then if the block size was 8k. You can still
I'd qualify that by including: "with raw data files".
With anything other than that, the I/O size is pretty much
fixed to what the f/s thinks is best and there is very little
one can do about it. Except use direct I/O (if it works in
your platform) or raw.
So many variables, so little time to test them all...
--
Cheers
Nuno Souto
in sunny Sydney, Australia
dbvision_at_optusnet.com.au
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request_at_freelists.org
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
-----------------------------------------------------------------
Received on Mon Jun 21 2004 - 05:33:49 CDT
