From: Jean-David Beyer <jeandavid8@verizon.net>
To: pgsql-performance@postgresql.org
Subject: Re: hardware upgrade, performance degrade?
Date: Sun, 03 Mar 2013 15:34:53 -0500
Message-ID: <5133B3ED.7000906@verizon.net> (raw)
In-Reply-To: <5133AF87.9040704@agliodbs.com>
References: <CALvesgn0Urm0Mj5HD-tM_-0Vw=4A-_O98Q+cxJ7NNXf7me+vcg@mail.gmail.com>
<CAFwQ8rc+POTz7USK0siefnSwC5R_ZMX4yhtmiWPjKZttedG9Zw@mail.gmail.com>
<CALvesgnv9AGR5Vo2BRqA62-PWB_63mvg7P5K6LGeoHhXh+fMiQ@mail.gmail.com>
<5133AF87.9040704@agliodbs.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 03/03/2013 03:16 PM, Josh Berkus wrote:
> Steven,
>
>> We saw the same performance problems when this new hardware was running
>> cent 6.3 with a 2.6.32-279.19.1.el6.x86_64 kernel and when it was matched
>> to the OS/kernel of the old hardware which was cent 5.8 with
>> a 2.6.18-308.11.1.el5 kernel.
>
> Oh, now that's interesting. We've been seeing the same issue (IO stalls
> on COMMIT) ond had attributed it to some bugs in the 3.2 and 3.4
> kernels, partly because we don't have a credible "old server" to test
> against. Now you have me wondering if there's not a hardware or driver
> issue with a major HW manufacturer which just happens to be hitting
> around now.
>
> Can you detail your hardware stack so that we can compare notes?
>
>
The current Red Hat Enterprise Linux 6.4 kernel is
kernel-2.6.32-358.0.1.el6.x86_64
in case that matters.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: jeandavid8@verizon.net
Subject: Re: hardware upgrade, performance degrade?
In-Reply-To: <5133B3ED.7000906@verizon.net>
* 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