Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id A3CD42E014B for ; Wed, 13 Feb 2008 13:46:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 35002-06 for ; Wed, 13 Feb 2008 13:46:48 -0400 (AST) Received: from is.rice.edu (is.rice.edu [128.42.42.24]) by postgresql.org (Postfix) with ESMTP id E725B2E014C for ; Wed, 13 Feb 2008 13:46:49 -0400 (AST) Received: from scan1.mail.rice.edu (scan1.mail.rice.edu [128.42.58.160]) by is.rice.edu (Postfix) with ESMTP id 100B541820; Wed, 13 Feb 2008 11:46:48 -0600 (CST) Received: from is.rice.edu ([128.42.42.24]) by scan1.mail.rice.edu (scan1.mail.rice.edu [128.42.58.160]) (amavisd-new, port 10024) with ESMTP id 07237-07; Wed, 13 Feb 2008 11:46:47 -0600 (CST) Received: by is.rice.edu (Postfix, from userid 18612) id 5880541819; Wed, 13 Feb 2008 11:46:47 -0600 (CST) Date: Wed, 13 Feb 2008 11:46:47 -0600 From: Kenneth Marshall To: Peter Koczan Cc: pgsql-performance Subject: Re: Anyone using a SAN? Message-ID: <20080213174647.GK12156@it.is.rice.edu> References: <4544e0330802130856t10582294lfa93bc91e234ed01@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4544e0330802130856t10582294lfa93bc91e234ed01@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) X-Virus-Scanned: by amavis-2.2.1 at scan1.mail.rice.edu X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/142 X-Sequence-Number: 28684 On Wed, Feb 13, 2008 at 10:56:54AM -0600, Peter Koczan wrote: > Hi all, > > We're considering setting up a SAN where I work. Is there anyone using > a SAN, for postgres or other purposes? If so I have a few questions > for you. > > - Are there any vendors to avoid or ones that are particularly good? > > - What performance or reliability implications exist when using SANs? > > - Are there any killer features with SANs compared to local storage? > > Any other comments are certainly welcome. > > Peter > Peter, The key is to understand your usage patterns, both I/O and query. SANs can be easily bandwidth limited which can tank your database performance. There have been several threads in the mailing list about performance problems caused by the use of a SAN for storage. Cheers, Ken