pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Stef <svb@ucs.co.za>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres low end processing.
Date: Mon, 6 Oct 2003 11:21:20 -0700
Message-ID: <200310061121.20681.josh@agliodbs.com> (raw)
In-Reply-To: <20031006095551.1d7bfeb8.svb@ucs.co.za>
References: <20031003163040.3641f39a.svb@ucs.co.za>
	<200310031108.49002.josh@agliodbs.com>
	<20031006095551.1d7bfeb8.svb@ucs.co.za>

Stef,

> => 1. Make sure that the WAL files (pg_xlog) are on a seperate disk from the 
> => database files, either through mounting or symlinking.
>  
> I'm not sure I understand how this helps?

It gives you better fsync write performance on a low-end disk setup.   
Otherwise, the disk is forced to do a hop-back-and-forth between the database 
and the xlog, resulting in much slower updates and thus the database tying up 
blocks of RAM longer -- particularly if your shared_buffers are set very low, 
which they will be.

On RAID setups, this is unnecessary becuase the RAID takes care of disk access 
management.  But on a low-end, 2-IDE-disk machine, you have to do it.

-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco




view thread (17+ messages)  latest in thread

Message-ID: <200310061121.20681.josh@agliodbs.com>
Permalink:  ../200310061121.20681.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200310061121.20681.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, svb@ucs.co.za
  Subject: Re: Postgres low end processing.
  In-Reply-To: <200310061121.20681.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