pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Cramer <pg@fastcrypt.com>
To: postgresql performance list <pgsql-performance@postgresql.org>
Subject: best use of an EMC SAN
Date: Wed, 11 Jul 2007 09:03:27 -0400
Message-ID: <D02C9DBC-0127-4B62-ABE3-93646B6A3F9F@fastcrypt.com> (raw)

Assuming we have 24 73G drives is it better to make one big metalun  
and carve it up and let the SAN manage the where everything is, or is  
it better to specify which spindles are where.

Currently we would require 3 separate disk arrays.

one for the main database, second one for WAL logs, third one we use  
for the most active table.

Problem with dedicating the spindles to each array is that we end up  
wasting space. Are the SAN's smart enough to do a better job if I  
create one large metalun and cut it up ?

Dave



view thread (11+ messages)  latest in thread

Message-ID: <D02C9DBC-0127-4B62-ABE3-93646B6A3F9F@fastcrypt.com>
Permalink:  ../D02C9DBC-0127-4B62-ABE3-93646B6A3F9F@fastcrypt.com/
Also on:    postgresql.org/message-id/D02C9DBC-0127-4B62-ABE3-93646B6A3F9F@fastcrypt.com

 · 

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: pg@fastcrypt.com
  Subject: Re: best use of an EMC SAN
  In-Reply-To: <D02C9DBC-0127-4B62-ABE3-93646B6A3F9F@fastcrypt.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