Re: Async writes or multiple DBWRs?

It's not a definitive answer because definitive answers can't match all sites.
Don't think only in database terms. There's the operating system too. So, if you turn off async reads and writes and therefore startup 3 database writers, the operating system will perform more dbwriter cycles then if there is only one db writer. So the answer is: As long as there are not too many server processes waiting for free blocks you better set async reads and writes, because db writer works fine and the process time will better spend on server processes. Finally, if server processes are waiting for db writer then you'll better start up more db writers.

I'll hope, that will help you.

Andreas Prusch

In article <6kh8kv$9td$1_at_nnrp1.dejanews.com>,   tgp_at_mci2000.com wrote:
>
>
> I'm looking for a definitive answer to the
> question: Given that I am running Oracle on AIX
> 4.2.1, with all Oracle database files on JFS, and
> not on raw partitions, should I use async I/O, or
> multiple DBWR processes?
>
> I have found scattered references to the two
> options in various books and manuals, and
> concluded that I should use async writes. Then an
> Oracle consultant guy I know who seems intelligent
> (but you know consultants!) said he "thinks he
> read somewhere" that you shouldn't use async
> writes on JFS files, but only on raw partitions.
>
> Can someone give me a convincing argument for
> using one or the other, or point me to holy Oracle
> documentation that answers the question?
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/ Now offering spam-free web-based newsreading
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading Received on Thu May 28 1998 - 01:39:57 CDT