From: Josh Berkus <josh@agliodbs.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Major Linux performance regression; shouldn't we be worried about RHEL6?
Date: Fri, 05 Nov 2010 13:32:44 -0700
Message-ID: <4CD469EC.4090702@agliodbs.com> (raw)
In-Reply-To: <AANLkTinDe5AeHt-aztr5VZFpz=i65tus0NyxmcsJTvFa@mail.gmail.com>
References: <4CD465D8.4070007@agliodbs.com>
<AANLkTinDe5AeHt-aztr5VZFpz=i65tus0NyxmcsJTvFa@mail.gmail.com>
> Why would it be off limits? Is it likely to lose data due to power failure etc?
If fsyncs are taking 5X as long, people can't use PostgreSQL on that
platform.
> Are you referring to improvements due to write barrier support getting
> fixed up fr ext4 to run faster but still be safe? I would assume that
> any major patches that increase performance with write barriers
> without being dangerous for your data would get back ported by RH as
> usual.
Hopefully, yes. I wouldn't mind confirmation of this, though; it
wouldn't be the first time RH shipped with known-bad IO performance.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
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: josh@agliodbs.com, scott.marlowe@gmail.com
Subject: Re: Major Linux performance regression; shouldn't we be worried about RHEL6?
In-Reply-To: <4CD469EC.4090702@agliodbs.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