pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: David Lang <dlang@invendra.net>
Cc: Anjan Dave <adave@vantage.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: separate drives for WAL or pgdata files
Date: Tue, 20 Dec 2005 13:52:20 -0600
Message-ID: <20051220195220.GK28771@pervasive.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0512191909240.2807@qnivq.ynat.uz>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF785098F10@vt-pe2550-001.vantage.vantage.com>
	<Pine.LNX.4.62.0512191909240.2807@qnivq.ynat.uz>

On Mon, Dec 19, 2005 at 07:20:56PM -0800, David Lang wrote:
> for persistant storage you can replicate from your ram-based system to a 
> disk-based system, and as long as your replication messages hit disk 
> quickly you can allow the disk-based version to lag behind in it's updates 
> during your peak periods (as long as it is able to catch up with the 
> writes overnight), and as the disk-based version won't have to do the 
> seeks for the reads it will be considerably faster then if it was doing 
> all the work (especially if you have good, large  battery-backed disk 
> caches to go with those drives to consolodate the writes)

Huh? Unless you're doing a hell of a lot of writing just run a normal
instance and make sure you have enough bandwidth to the drives with
pg_xlog on it. Make sure those drives are using a battery-backed raid
controller too. You'll also need to tune things to make sure that
checkpoints never have much (if any) work to do when the occur, but you
should be able to set that up with proper bg_writer tuning.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (4+ messages)

Message-ID: <20051220195220.GK28771@pervasive.com>
Permalink:  ../20051220195220.GK28771@pervasive.com/
Also on:    postgresql.org/message-id/20051220195220.GK28771@pervasive.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: jnasby@pervasive.com, dlang@invendra.net, adave@vantage.com
  Subject: Re: separate drives for WAL or pgdata files
  In-Reply-To: <20051220195220.GK28771@pervasive.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