pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Aditya <aditya@grot.org>
To: Joe Conway <mail@joeconway.com>
Cc: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: sfpug@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [sfpug] DATA directory on network attached storage
Date: Mon, 11 Apr 2005 18:20:32 +0000
Message-ID: <20050411182032.GA48183@mighty.grot.org> (raw)
In-Reply-To: <425ABB17.305@joeconway.com>
References: <200502091350.24885.josh@agliodbs.com>
	<Pine.LNX.4.62.0504080957220.11558@discord.dyndns.org>
	<20050408192136.GD72199@mighty.grot.org>
	<425ABB17.305@joeconway.com>

On Mon, Apr 11, 2005 at 10:59:51AM -0700, Joe Conway wrote:
> >FWIW, if I were to do this anew, I would probably opt for iSCSI over GigE 
> >with
> >a NetApp.
> 
> Any particular reason? Our NetApp technical rep advised nfs over iSCSI, 
> IIRC because of performance.

I would mount the Netapp volume(s) as a block level device on my server using
iSCSI (vs. a file-based device like NFS) so that filesystem parameters could
be more finely tuned and one could really make use of jumbo frames over GigE.

But that level of tuning depends on load after all and with a Netapp you can
have both, so maybe start with having your databases on an NFS volume on the
Netapp, and when you have a better idea of the tuning requirements, move it
over to a iSCSI LUN.

I'm not sure I understand why NFS would perform better than iSCSI -- in any
case, some large Oracle dbs at my current job are moving to iSCSI on Netapp
and in that environment both Oracle and Netapp advise iSCSI (probably because
Oracle uses the block-level device directly), so I suspend the difference in
performance is minimal.

Adi



view thread (7+ messages)  latest in thread

Message-ID: <20050411182032.GA48183@mighty.grot.org>
Permalink:  ../20050411182032.GA48183@mighty.grot.org/
Also on:    postgresql.org/message-id/20050411182032.GA48183@mighty.grot.org

 · 

reply

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: aditya@grot.org, mail@joeconway.com, jeff@frostconsultingllc.com, josh@agliodbs.com, sfpug@postgresql.org
  Subject: Re: [sfpug] DATA directory on network attached storage
  In-Reply-To: <20050411182032.GA48183@mighty.grot.org>

* 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