From: Alex Deucher <alexdeucher@gmail.com>
To: Kenneth Marshall <ktm@rice.edu>
Cc: Peter Koczan <pjkoczan@gmail.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Anyone using a SAN?
Date: Wed, 13 Feb 2008 12:58:03 -0500
Message-ID: <a728f9f90802130958q64d80dafue6118175f331ba64@mail.gmail.com> (raw)
In-Reply-To: <20080213174647.GK12156@it.is.rice.edu>
References: <4544e0330802130856t10582294lfa93bc91e234ed01@mail.gmail.com>
<20080213174647.GK12156@it.is.rice.edu>
On Feb 13, 2008 12:46 PM, Kenneth Marshall <ktm@rice.edu> wrote:
> 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.
It's critical that you set up the SAN with a database in mind
otherwise the performance will be bad. I tested a DB on a SAN
designed to maximize storage space and performance was terrible. I
never had the time or resources to reconfigure the SAN to test a more
suitable spindle setup since the SAN was in heavy production use for
file archiving.
Alex
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: alexdeucher@gmail.com, ktm@rice.edu, pjkoczan@gmail.com
Subject: Re: Anyone using a SAN?
In-Reply-To: <a728f9f90802130958q64d80dafue6118175f331ba64@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