Re: enabling dnfs when it's not being used

From: Martin Berger <martin.a.berger_at_gmail.com>
Date: Fri, 6 Feb 2015 15:15:57 +0100
Message-ID: <CALH8A9141BBFoF4OnTmn2Mu+6nQNxXDuwtjGac36R3JZ2SRg7Q_at_mail.gmail.com>

As long as you do not need any other ODM library in those setups I assume it just doesn't matter.
If the code is not used at all, only the mapped .so in memory might differ in size. But I hope you do not need those few kb saved.

 Martin

On Fri, Feb 6, 2015 at 3:02 PM, Jeremy Schneider < jeremy.schneider_at_ardentperf.com> wrote:

> does anyone know any downsides to enabling dnfs when it's not being
> used? (i.e. the db is using regular local filesystem and/or ASM.)
>
> context is that i create standard builds which get cloned to a whole
> bunch of environments. i have a few environments that use dNFS and
> i'm thinking about just enabling it by default in my standard build
> that gets pushed everywhere. my heaviest workload environments don't
> use dNFS and currently it's not enabled on those homes; i'm wondering
> if there would be any potential risk to enabling it there.
>
> -Jeremy
>
> --
> http://about.me/jeremy_schneider
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

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

Received on Fri Feb 06 2015 - 15:15:57 CET