Re: db_file_multiblock_read_count and 10g

From: Martin Berger <martin.a.berger_at_gmail.com>
Date: Mon, 26 Jan 2009 06:21:06 +0100
Message-Id: <62D468FE-55BC-415E-81C0-25B283EB84BE_at_gmail.com>



Greg,

to shorten your research a little bit,
in 11.1.0.7 _db_* parameters seems not to be affected by cpu_count (up to 128 CPUs)
I run a test there and didn't find it changing: http://berxblog.blogspot.com/2009/01/instance-parameters-derived-from.html Sorry, it's not 10g. Maybe I get the resources to run it on 10gR2 also.

But I'm very interrested if the cache changes anything, especially if it's different in manual or AMM configuration.

br,
  Martin

01.2009 um 01:38 schrieb Greg Rahn:

>>
>> This is a reasonable assumption, but I'm not sure how Oracle
>> determines the
>> maximum I/O size. On my laptop, Oracle 10.2.0.1 and 11.1.0.6 show
>> quite
>> different _db_file_exec_read_count.
>>
>> In 10.2.0.1 : _db_file_exec_read_count = 5
>> In 11.1.0.6 : _db_file_exec_read_count = 128
>>
>> It seems quite dependent on Oracle version, not just on OS and/or
>> storage
>> settings.
>
> Going from memory and not looking at the code, I think the db cache
> size and number of processes also influence it, and I don't recall if
> this changed between releases or not.



--
http://www.freelists.org/webpage/oracle-l


  • application/pkcs7-signature attachment: smime.p7s
Received on Sun Jan 25 2009 - 23:21:06 CST

Original text of this message