From: Greg Smith <greg@2ndquadrant.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Major Linux performance regression; shouldn't we be worried about RHEL6?
Date: Fri, 05 Nov 2010 14:26:16 -0700
Message-ID: <4CD47678.5050002@2ndquadrant.com> (raw)
In-Reply-To: <4CD465D8.4070007@agliodbs.com>
References: <4CD465D8.4070007@agliodbs.com>
Josh Berkus wrote:
> Domas (of Facebook/Wikipedia, MySQL geek) pointed me to this report:
>
> http://www.phoronix.com/scan.php?page=article&item=linux_perf_regressions&num=1
> http://www.phoronix.com/scan.php?page=article&item=ext4_then_now&num=6
>
The main change here was discussed back in January:
http://archives.postgresql.org/message-id/4B512D0D.4030909@2ndquadrant.com
What I've been doing about this is the writing leading up to
http://wiki.postgresql.org/wiki/Reliable_Writes so that when RHEL6 does
ship, we have a place to point people toward that makes it better
documented that the main difference here is a reliability improvement
rather than a performance regression. I'm not sure what else we can do
here, other than organizing more testing for kernel bugs in this area on
RHEL6. The only way to regain the majority of the "lost" performance
here is to turn off synchronous_commit in the default config.
--
Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services and Support www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books
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, josh@agliodbs.com
Subject: Re: Major Linux performance regression; shouldn't we be worried about RHEL6?
In-Reply-To: <4CD47678.5050002@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