pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Jeffrey W. Baker <jwbaker@acm.org>
Cc: Steve Poe <spoe@sfnet.cc>
Cc: paul@oxton.com
Subject: Re: [SPAM?] Re: PG8 Tuning
Date: Tue, 16 Aug 2005 09:12:31 -0700
Message-ID: <200508160912.32263.josh@agliodbs.com> (raw)
In-Reply-To: <1123779524.6664.1.camel@toonses.gghcwest.com>
References: <1536.217.45.209.171.1123763001.squirrel@www.gradwell.com>
	<1123836428.19976.26.camel@amd64-laptop-spoe>
	<1123779524.6664.1.camel@toonses.gghcwest.com>

Jeff,

> > 4) pg_xlog: If you're pg_xlog is on a spindle is *only* for pg_xlog
> > you're better off.
>
> Like Mr. Stone said earlier, this is pure dogma.  In my experience,
> xlogs on the same volume with data is much faster if both are on
> battery-backed write-back RAID controller memory.  Moving from this
> situation to xlogs on a single normal disk is going to be much slower in
> most cases.

The advice on separate drives for xlog (as is all advice on that web page) is 
based on numerous, repeatable tests at OSDL.    

However, you are absolutely correct in that it's *relative* advice, not 
absolute advice.   If, for example, you're using a $100,000 EMC SAN as your 
storage you'll probably be better off giving it everything and letting its 
controller and cache handle disk allocation etc.   On the other hand, if 
you're dealing with the 5 drives in a single Dell 6650, I've yet to encounter 
a case where a separate xlog disk did not benefit an OLTP application.

For Solaris, the advantage of using a separate disk or partition is that the 
mount options you want for the xlog (including forcedirectio) are 
considerably different from what you'd use with the main database.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (19+ messages)  latest in thread

Message-ID: <200508160912.32263.josh@agliodbs.com>
Permalink:  ../200508160912.32263.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200508160912.32263.josh@agliodbs.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: josh@agliodbs.com, jwbaker@acm.org, spoe@sfnet.cc, paul@oxton.com
  Subject: Re: [SPAM?] Re: PG8 Tuning
  In-Reply-To: <200508160912.32263.josh@agliodbs.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