pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: High CPU usage / load average after upgrading to Ubuntu 12.04
Date: Tue, 19 Feb 2013 15:24:31 -0800
Message-ID: <512409AF.8010308@agliodbs.com> (raw )
In-Reply-To: <5123BB94.7030603@agliodbs.com >
References: <60B572D9298D944580F7D51195DD30804357FA4ABF@VMBX125.ihostexchange.net >
<60B572D9298D944580F7D51195DD30804357FA4B60@VMBX125.ihostexchange.net >
<dpg5ol29ltnb072ngdg8auj4.1360707457411@email.android.com >
<60B572D9298D944580F7D51195DD30804357FA4C11@VMBX125.ihostexchange.net >
<511BE879.8080706@agliodbs.com >
<511C2F10.3080409@agliodbs.com >
<60B572D9298D944580F7D51195DD30804357FA4DE2@VMBX125.ihostexchange.net >
<511D2F11.6040706@agliodbs.com >
<60B572D9298D944580F7D51195DD308043580CAA0B@VMBX125.ihostexchange.net >
<511D79FE.7060705@agliodbs.com >
<60B572D9298D944580F7D51195DD308043580CAA87@VMBX125.ihostexchange.net >
<CAOR=d=3CqRL5jrFRTSg9kFdcJzKpx3TJSsoDwRqpPUO=ENoFRQ@mail.gmail.com >
<511E7DC0.4090506@agliodbs.com >
<CAOR=d=2cEi=ibGS4DCrFAWq8VtCz6XEYDsMyarBX=evshLWgKg@mail.gmail.com >
<5122C507.7060303@agliodbs.com >
<CAOR=d=3bXmMmTvh3cKCizhwsijxg6wh6ADC053w-dbkC3e_zCQ@mail.gmail.com >
<5122C9D9.9040909@agliodb s.com >
<5122FF50.8030903@catalyst.net.nz >
<5123BB94.7030603@agliodb! s.com >
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 02/19/2013 09:51 AM, Josh Berkus wrote:
> On 02/18/2013 08:28 PM, Mark Kirkwood wrote:
>> Might be worth looking at your vm.dirty_ratio, vm.dirty_background_ratio
>> and friends settings. We managed to choke up a system with 16x SSD by
>> leaving them at their defaults...
>
> Yeah? Any settings you'd recommend specifically? What did you use on
> the SSD system?
>
NM, I tested lowering dirty_background_ratio, and it didn't help,
because checkpoints are kicking in before pdflush ever gets there.
So the issue seems to be that if you have this combination of factors:
1. large RAM
2. many/fast CPUs
3. a database which fits in RAM but is larger than the RAID controller's
WB cache
4. pg_xlog on the same volume as pgdata
... then you'll see checkpoint "stalls" and spread checkpoint will
actually make them worse by making the stalls longer.
Moving pg_xlog to a separate partition makes this better. Making
bgwriter more aggressive helps a bit more on top of that.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
view thread (33+ messages) latest in thread
Message-ID: <512409AF.8010308@agliodbs.com>
Permalink: ../512409AF.8010308@agliodbs.com/
Also on: postgresql.org/message-id/512409AF.8010308@agliodbs.com
copy link · copy postgr.es
reply 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
Subject: Re: High CPU usage / load average after upgrading to Ubuntu 12.04
In-Reply-To: <512409AF.8010308@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