pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve Poe <spoe@sfnet.cc>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Ideal disk setup for Postgresql 7.4?
Date: Wed, 26 Jan 2005 16:39:49 -0500
Message-ID: <20267.1106775589@sss.pgh.pa.us> (raw)
In-Reply-To: <41F79610.20003@sfnet.cc>
References: <41F63424.1060904@sfnet.cc>
	<200501251903.09734.josh@agliodbs.com>
	<41F6DBD8.2050008@sfnet.cc>
	<200501261003.15267.josh@agliodbs.com>
	<41F79610.20003@sfnet.cc>

Steve Poe <spoe@sfnet.cc> writes:
>> Well, it's less bad with 7 disks than it is with 3, certainly.   However,there 
>> is an obvious and quick gain to be had by splitting off the WAL logs onto 
>> their own disk resource ... up to 14%+ performance in some applications.
>> 
> Pardon my ignorance, but the WAL logs are comprised of pg_xlog and 
> pg_clog? Their own disk resource, but not within the same channel of 
> disks the database is on, right?

Just pg_xlog.  Ideally you don't want any other traffic on the physical
disk pg_xlog is on --- the idea is that the write heads need to stay
over the current xlog file.  I don't think it hurts too much to share a
controller channel though.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <20267.1106775589@sss.pgh.pa.us>
Permalink:  ../20267.1106775589@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/20267.1106775589@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, spoe@sfnet.cc, josh@agliodbs.com
  Subject: Re: Ideal disk setup for Postgresql 7.4?
  In-Reply-To: <20267.1106775589@sss.pgh.pa.us>

* 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