pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alan Hodgson <ahodgson@simkin.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Advice configuring ServeRAID 8k for performance
Date: Thu, 5 Aug 2010 11:53:10 -0700
Message-ID: <201008051153.11130@hal.medialogik.com> (raw)
In-Reply-To: <op.vgy9k5ov5ru9c3@kent60.office.vivox.com>
References: <op.vgy9k5ov5ru9c3@kent60.office.vivox.com>

On Thursday, August 05, 2010, "Kenneth Cox" <kenstir@gmail.com> wrote:
> 1) Should I switch to RAID 10 for performance?  I see things like "RAID 5
> is bad for a DB" and "RAID 5 is slow with <= 6 drives" but I see little
> on RAID 6.  RAID 6 was the original choice for more usable space with
> good redundancy.  My current performance is 85MB/s write, 151 MB/s reads
> (using dd of 2xRAM per
> http://www.westnet.com/~gsmith/content/postgresql/pg-disktesting.htm).

If you can spare the drive space, go to RAID 10. RAID 5/6 usually look fine 
on single-threaded sequential tests (unless your controller really sucks), 
but in the real world with multiple processes doing random I/O RAID 10 will 
go a lot further on the same drives. Plus your recovery time from disk 
failures will be a lot faster.

If you can't spare the drive space ... you should buy more drives. 

> 
> 2) Should I configure the ext3 file system with noatime and/or
> data=writeback or data=ordered?  My controller has a battery, the logical
> drive has write cache enabled (write-back), and the physical devices have
> write cache disabled (write-through).

noatime is fine but really minor filesystem options rarely show much impact. 
My best performance comes from XFS filesystems created with stripe options 
matching the underlying RAID array. Anything else is just a bonus.

> * I know "feels slow" is not scientific.  What I mean is that any single
> query on a fact table, or any 'rm -rf' of a big directory sends disk
> utilization to 100% (measured with iostat -x 3).

.. and it should. Any modern system can peg a small disk array without much 
effort. Disks are slow.

-- 
"No animals were harmed in the recording of this episode. We tried but that 
damn monkey was just too fast."



view thread (33+ messages)  latest in thread

Message-ID: <201008051153.11130@hal.medialogik.com>
Permalink:  ../201008051153.11130@hal.medialogik.com/
Also on:    postgresql.org/message-id/201008051153.11130@hal.medialogik.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: ahodgson@simkin.ca
  Subject: Re: Advice configuring ServeRAID 8k for performance
  In-Reply-To: <201008051153.11130@hal.medialogik.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