Re: Need to tune for Heavy Write

From: "Nicholson, Brad (Toronto, ON, CA)" <bnicholson(at)hp(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Willy-Bas Loos <willybas(at)gmail(dot)com>
Cc: Adarsh Sharma <adarsh(dot)sharma(at)orkash(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Need to tune for Heavy Write
Date: 2011-08-04 12:41:47
Message-ID: 2626AEE4839D064CB0472A3814DC403F46DA2F2222@GVW1092EXB.americas.hpqcorp.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> -----Original Message-----
> From: pgsql-performance-owner(at)postgresql(dot)org [mailto:pgsql-performance-
> owner(at)postgresql(dot)org] On Behalf Of Scott Marlowe
> Sent: Thursday, August 04, 2011 4:46 AM
> To: Willy-Bas Loos
> Cc: Adarsh Sharma; pgsql-performance(at)postgresql(dot)org
> Subject: Re: [PERFORM] Need to tune for Heavy Write
>
>
> > Moving the pg_xlog to a different directory only helps when that
> > directory is on a different harddisk (or whatever I/O device).
>
> Not entirely true. By simply being on a different mounted file
> system this moves the fsync calls on the pg_xlog directories off of
> the same file system as the main data store. Previous testing has
> shown improvements in performance from just using a different file
> system.
>

Is this still the case for xfs or ext4 where fsync is properly flushing only the correct blocks to disk, or was this referring to the good old ext3 flush everything on fysnc issue?

Brad.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Nassib Nassar 2011-08-04 13:40:08 Seq Scan vs. Index Scan
Previous Message Dusan Misic 2011-08-04 09:03:13 Re: Need to tune for Heavy Write