From: Greg Smith <greg@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
Cc: 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 16:13:22 -0400
Message-ID: <4C699BE2.50606@2ndquadrant.com> (raw)
In-Reply-To: <20100816200227.GA3911@anarazel.de>
References: <201008131817.o7DIH1b03550@momjian.us>
<4C6591D9.1080206@2ndquadrant.com>
<5687A8AD-CA70-4272-A32C-6AE5F491CEA4@richrelevance.com>
<4C69796D.9000408@2ndquadrant.com>
<20100816200227.GA3911@anarazel.de>
Andres Freund wrote:
> Or use -o sync. Or configure a ridiciuosly low dirty_memory amount
> (which has a problem on large systems because 1% can still be too
> much. Argh.)...
>
-o sync completely trashes performance, and trying to set the
dirty_ratio values to even 1% doesn't really work due to things like the
"congestion avoidance" code in the kernel. If you sync a lot more
often, which putting the WAL on the same disk as the database
accidentally does for you, that works surprisingly well at avoiding this
whole class of problem on ext3. A really good solution is going to take
a full rewrite of the PostgreSQL checkpoint logic though, which will get
sorted out during 9.1 development. (cue dramatic foreshadowing music here)
--
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, andres@anarazel.de, scott@richrelevance.com, bruce@momjian.us, kenstir@gmail.com
Subject: Re: Advice configuring ServeRAID 8k for performance
In-Reply-To: <4C699BE2.50606@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