From: Greg Smith <greg@2ndquadrant.com>
To: Scott Carey <scott@richrelevance.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Kenneth Cox <kenstir@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Advice configuring ServeRAID 8k for performance
Date: Mon, 16 Aug 2010 13:46:21 -0400
Message-ID: <4C69796D.9000408@2ndquadrant.com> (raw)
In-Reply-To: <5687A8AD-CA70-4272-A32C-6AE5F491CEA4@richrelevance.com>
References: <201008131817.o7DIH1b03550@momjian.us>
<4C6591D9.1080206@2ndquadrant.com>
<5687A8AD-CA70-4272-A32C-6AE5F491CEA4@richrelevance.com>
Scott Carey wrote:
> This is because an fsync on ext3 flushes _all dirty pages in the file system_ to disk, not just those for the file being fsync'd.
> One partition for WAL, one for data. If using ext3 this is essentially a performance requirement no matter how your array is set up underneath.
>
Unless you want the opposite of course. Some systems split out the WAL
onto a second disk, only to discover checkpoint I/O spikes become a
problem all of the sudden after that. The fsync calls for the WAL
writes keep the write cache for the data writes from ever getting too
big. This slows things down on average, but makes the worst case less
stressful. Free lunches are so hard to find nowadays...
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.us
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: greg@2ndquadrant.com, scott@richrelevance.com, bruce@momjian.us, kenstir@gmail.com
Subject: Re: Advice configuring ServeRAID 8k for performance
In-Reply-To: <4C69796D.9000408@2ndquadrant.com>
* 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