pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Himanshu Baweja <himanshubaweja@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Moving pg_xlog
Date: Thu, 02 Jun 2005 10:23:23 -0400
Message-ID: <13548.1117722203@sss.pgh.pa.us> (raw)
In-Reply-To: <20050602070209.96753.qmail@web51005.mail.yahoo.com>
References: <20050602070209.96753.qmail@web51005.mail.yahoo.com>

Himanshu Baweja <himanshubaweja@yahoo.com> writes:
> My database has two scsi disks....
> my current configuration has pg_xlog on disk1 and data on disk2....
> the machine is used for database only....
> now did some logging and came to a conclusion that my disk2(data disk) is getting used around 3 times more than disk1(pg_xlog)....
 
> so wht is recommended... move some of the data to disk1 so that both disks are equally used... by creating tablespaces or let my configuration be whts its currently... iowait is one of the bottlenecks in my application performance.....

It seems highly unlikely that putting more stuff on the xlog disk will
improve performance --- at least not if your bottleneck is update speed.
If it's a read-mostly workload then optimizing xlog writes may not be
the most important thing to you.  In that case you might want to ignore
xlog and try something along the lines of tables on one disk, indexes
on the other.

			regards, tom lane



view thread (10+ messages)  latest in thread

Message-ID: <13548.1117722203@sss.pgh.pa.us>
Permalink:  ../13548.1117722203@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/13548.1117722203@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, himanshubaweja@yahoo.com
  Subject: Re: Moving pg_xlog
  In-Reply-To: <13548.1117722203@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