Re: Raid settings
From: MJ Mody <emjay.mody_at_gmail.com>
Date: Thu, 3 Mar 2016 15:51:07 -0600
Message-Id: <FE74F406-6797-472D-9CBE-CB8B24B25C37_at_gmail.com>
It is assumed such features could be vendor dependent. As such if vendor is willing to share documentation, this would be helpful. I remember setting both settings at controller level to medium or 50%. One can easily argue that there is certain benefit or trade-off on 75%/25% write vs read or the opposite. A dependency here is identification of application(s)/db infrastructure and an end goal. A sincere recommendation is to vet this out in a development/sandbox environment prior to promoting to test/prod.
Date: Thu, 3 Mar 2016 15:51:07 -0600
Message-Id: <FE74F406-6797-472D-9CBE-CB8B24B25C37_at_gmail.com>
It is assumed such features could be vendor dependent. As such if vendor is willing to share documentation, this would be helpful. I remember setting both settings at controller level to medium or 50%. One can easily argue that there is certain benefit or trade-off on 75%/25% write vs read or the opposite. A dependency here is identification of application(s)/db infrastructure and an end goal. A sincere recommendation is to vet this out in a development/sandbox environment prior to promoting to test/prod.
Cheers
> On Mar 3, 2016, at 1:23 PM, Storey, Robert (DCSO) <RStorey_at_DCSO.nashville.org> wrote:
>
> When configuring raids, what seems to be the consensus on doing Read Ahead? By normal practice I always ask for the raid holding the database to be Write Through, but I’ve never really looked at the Read Ahead.
>
> Any thoughts or good/bad reasons for setting this on/off?
>
> Just curious.
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Mar 03 2016 - 22:51:07 CET