pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: What to do with 6 disks?
Date: Tue, 19 Apr 2005 20:06:54 -0700
Message-ID: <d44h0e$2prl$1@news.hub.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0504191756280.25755@discord.dyndns.org>
References: <200504191610.j3JGAM820841@candle.pha.pa.us>
	<OF555C0C8C.E17C1A26-ON05256FE8.0059549C-05256FE8.0059EE74@ftw.us.ray.com>
	<20050420001523.GU58835@decibel.org>
	<Pine.LNX.4.62.0504191756280.25755@discord.dyndns.org>

My experience:

1xRAID10 for postgres
1xRAID1 for OS + WAL


Jeff Frost wrote:
> Now that we've hashed out which drives are quicker and more money equals 
> faster...
> 
> Let's say you had a server with 6 separate 15k RPM SCSI disks, what raid 
> option would you use for a standalone postgres server?
> 
> a) 3xRAID1 - 1 for data, 1 for xlog, 1 for os?
> b) 1xRAID1 for OS/xlog, 1xRAID5 for data
> c) 1xRAID10 for OS/xlong/data
> d) 1xRAID1 for OS, 1xRAID10 for data
> e) .....
> 
> I was initially leaning towards b, but after talking to Josh a bit, I 
> suspect that with only 4 disks the raid5 might be a performance 
> detriment vs 3 raid 1s or some sort of split raid10 setup.
> 



view thread (5+ messages)  latest in thread

Message-ID: <d44h0e$2prl$1@news.hub.org>
Permalink:  ../d44h0e$2prl$1@news.hub.org/
Also on:    postgresql.org/message-id/d44h0e$2prl$1@news.hub.org

 · 

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: wyu@talisys.com
  Subject: Re: What to do with 6 disks?
  In-Reply-To: <d44h0e$2prl$1@news.hub.org>

* 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