pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Christiaan Willemsen <cwillemsen@technocon.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to setup disk spindles for best performance
Date: Wed, 20 Aug 2008 21:41:05 -0600
Message-ID: <dcc563d10808202041t16c45243q17b364dd151d419c@mail.gmail.com> (raw)
In-Reply-To: <972BDF1A-B4ED-46EC-B416-0CDF15A0439A@technocon.com>
References: <972BDF1A-B4ED-46EC-B416-0CDF15A0439A@technocon.com>

On Wed, Aug 20, 2008 at 4:25 PM, Christiaan Willemsen
<cwillemsen@technocon.com> wrote:
> I'm currently trying to find out what the best configuration is for our new
> database server. It will server a database of about 80 GB and growing fast.
> The new machine has plenty of memory (64GB) and 16 SAS disks, of wich two
> are already in use as a mirror for the OS.

Got almost the same setup with 32 Gig of ram...  I'm running the Areca
1680 controller with 512M battery backed cache and I'm quite happy
with the performance so far.

Mine is set up to use the OS mirror set for the pg_xlog as well, but
on a separate logical partition.  I figure the RAID controller will
even out the writes there to keep it fast.  The next 12 drives are a
RAID-10 set and the last two are hot spares.  On an array this big you
should always have at least one hot spare.

Generally breaking the disks up for index versus tables etc is a lot
of work for minimal gain.  A good RAID controller will make up for
having to do that, and usually do better, since if the indexes are
getting hit a LOT then you have all 12 disks in the RAID-10 working
together.

But what's your workload look like?  Lotsa updates, inserts, deletes,
big selects, bulk loads in the middle of the day, etc...?



view thread (11+ messages)  latest in thread

Message-ID: <dcc563d10808202041t16c45243q17b364dd151d419c@mail.gmail.com>
Permalink:  ../dcc563d10808202041t16c45243q17b364dd151d419c@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10808202041t16c45243q17b364dd151d419c@mail.gmail.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, cwillemsen@technocon.com
  Subject: Re: How to setup disk spindles for best performance
  In-Reply-To: <dcc563d10808202041t16c45243q17b364dd151d419c@mail.gmail.com>
  References: <972BDF1A-B4ED-46EC-B416-0CDF15A0439A@technocon.com> <dcc563d10808202041t16c45243q17b364dd151d419c@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