From: Dawid Kuroczko <qnex42@gmail.com>
To: Chris Hoover <revoohc@gmail.com>
Cc: PGSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL NetApp and NFS
Date: Fri, 21 Mar 2008 10:34:09 +0100
Message-ID: <758d5e7f0803210234l785b115as6f4b42f42fa97f13@mail.gmail.com> (raw)
In-Reply-To: <1d219a6f0803201232g54924fb3ka206c9b03e4664c7@mail.gmail.com>
References: <1d219a6f0803201232g54924fb3ka206c9b03e4664c7@mail.gmail.com>
On Thu, Mar 20, 2008 at 8:32 PM, Chris Hoover <revoohc@gmail.com> wrote:
> I just found out that my company is planning on migrating my databases from
> our current ISCSI storage solution to NetApps connected via NFS. I knew
> about the NetApp migration, but always assumed (and shame on me) that I
> would have direct attachments to the servers.
It is also possible to present block devices from NetApp over iSCSI or FC
(I am not sure about licensing model though). You get all the goodies
like thin provisioning (only non-zero blocks are allocated), snapshots and
all, but you see it as a block device. Works fine.
It is also worth to mention that NetApp utilizes somewhat "copy on write"
write strategy -- so whenever you modify a block, new version of the block
is written on its WAFL filesystem. In practical terms it is quite resilient to
random writes (and that read performance is not stellar ;)).
I didn't try putting database on NFS mount directly, but I know NetApp
advertises that such setups are being used with Oracle database
(and allegedly Oracle website's databases are on such setup).
So I would feel quite safe with such a setup.
Oh, and don't forget to set rsize and wsize to 8K-32K (test and write here
what gives best performance!).
Regards,
Dawid
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: qnex42@gmail.com, revoohc@gmail.com
Subject: Re: PostgreSQL NetApp and NFS
In-Reply-To: <758d5e7f0803210234l785b115as6f4b42f42fa97f13@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox