pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: shridhar_daithankar@persistent.co.in
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance advice
Date: Tue, 24 Jun 2003 10:18:57 -0400
Message-ID: <19141.1056464337@sss.pgh.pa.us> (raw)
In-Reply-To: <3EF85224.1633.3939548@localhost>
References: <3EF85224.1633.3939548@localhost>

"Shridhar Daithankar" <shridhar_daithankar@persistent.co.in> writes:
>> - Would a RAID setup make the disk faster?  Because top rarely shows the
>> CPUs above 50%, I suspect maybe the disk is the bottleneck.

> Yes it is. You need to move WAL to a different disk.

For an update-intensive setup, putting WAL on its own disk is definitely
your biggest win.  You might then find it rewarding to fool with the
wal_sync_method and perhaps to bump up wal_buffers a little.  A small
number of people have had luck with putting a nonzero commit_delay but
I have little faith in that.

			regards, tom lane



view thread (23+ messages)  latest in thread

Message-ID: <19141.1056464337@sss.pgh.pa.us>
Permalink:  ../19141.1056464337@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/19141.1056464337@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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, shridhar_daithankar@persistent.co.in
  Subject: Re: Performance advice
  In-Reply-To: <19141.1056464337@sss.pgh.pa.us>
  References: <3EF85224.1633.3939548@localhost> <19141.1056464337@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