RE: db_file_multiblock_read_count causing full scans to take longer?
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: <Christian.Antognini@xxxxxxxxxxxx>, "Don Seiler" <don@xxxxxxxxx>
- Date: Tue, 19 Dec 2006 13:00:50 -0700
Hi Christian,
By flushing the buffer cache before your testing, aren't you going to be
testing and optimizing based on an unrealistic scenario? Why tune for
all blocks being uncached if that will not be the typical case?
Thanks,
Brandon
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Christian Antognini
Therefore, to find the best db_file_multiblock_read_count, it makes
sense to flush the buffer cache before each FTS.
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
