From: | David Rees <drees76(at)gmail(dot)com> |
---|---|
To: | Scott Carey <scott(at)richrelevance(dot)com> |
Cc: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Raid 10 chunksize |
Date: | 2009-03-25 02:04:42 |
Message-ID: | 72dbd3150903241904t39a2304cv806b228cbaef3036@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Mar 24, 2009 at 6:48 PM, Scott Carey <scott(at)richrelevance(dot)com> wrote:
> Your xlogs are occasionally close to max usage too -- which is suspicious at
> 10MB/sec. There is no reason for them to be on ext3 since they are a
> transaction log that syncs writes so file system journaling doesn't mean
> anything. Ext2 there will lower the sync times and reduced i/o utilization.
I would tend to recommend ext3 in data=writeback and make sure that
it's mounted with noatime over using ext2 - for the sole reason that
if the system shuts down unexpectedly, you don't have to worry about a
long fsck when bringing it back up.
Performance between the two filesystems should really be negligible
for Postgres logging.
-Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-03-25 02:11:07 | Re: Raid 10 chunksize |
Previous Message | Scott Carey | 2009-03-25 01:48:36 | Re: Raid 10 chunksize |