From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Himanshu Baweja <himanshubaweja(at)yahoo(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Moving pg_xlog |
Date: | 2005-06-02 14:23:23 |
Message-ID: | 13548.1117722203@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Himanshu Baweja <himanshubaweja(at)yahoo(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Mindaugas Riauba | 2005-06-02 14:24:47 | Re: How to avoid database bloat |
Previous Message | Tom Lane | 2005-06-02 13:45:39 | Re: How to avoid database bloat |