pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steve Wampler <swampler@noao.edu>
To: Ketema Harris <ketema@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Running on an NFS Mounted Directory
Date: Wed, 26 Apr 2006 19:35:42 -0700
Message-ID: <20060427023542.GA14672@weaver.tuc.noao.edu> (raw)
In-Reply-To: <C0759F82.2C4E%ketema@gmail.com>
References: <C0759F82.2C4E%ketema@gmail.com>

On Wed, Apr 26, 2006 at 10:06:58PM -0400, Ketema Harris wrote:
> I was wondering if there were any performance issues with having a data
> directory that was an nfs mounted drive?  Say like a SAN or NAS device? Has
> anyone done this before?
 
My understanding is that NFS is pretty poor in performance in general,
so I would expect it to be particularly bad for a DB.  You might run
some (non-DB) performance tests to get a feel for how bad it might me.
(Someone once told me that NFS topped out at around 12MB/s, but I don't
know if that's really true [they were trying to sell a competitive
networked filesystem]).

In any event, you're at least limited by ethernet speeds, if not more.

-- 
Steve Wampler -- swampler@noao.edu
The gods that smiled on your birth are now laughing out loud.



view thread (19+ messages)  latest in thread

Message-ID: <20060427023542.GA14672@weaver.tuc.noao.edu>
Permalink:  ../20060427023542.GA14672@weaver.tuc.noao.edu/
Also on:    postgresql.org/message-id/20060427023542.GA14672@weaver.tuc.noao.edu

 · 

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: swampler@noao.edu, ketema@gmail.com
  Subject: Re: Running on an NFS Mounted Directory
  In-Reply-To: <20060427023542.GA14672@weaver.tuc.noao.edu>

* 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