From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Armand du Plessis <adp@bank.io>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Fwd: Problems with pg_locks explosion
Date: Tue, 02 Apr 2013 16:41:06 +1300
Message-ID: <515A5352.4030406@catalyst.net.nz> (raw)
In-Reply-To: <CANf99sWN4LP_xF012miq=MghCYtbm369bup9tVT1+BiTOR9sUA@mail.gmail.com>
References: <CANf99sX6dK9cG9PDhXARq70QybO3Tn7EkRwt_YPxp8Lo-AFhmQ@mail.gmail.com>
<515A2223.5080204@catalyst.net.nz>
<CANf99sWN4LP_xF012miq=MghCYtbm369bup9tVT1+BiTOR9sUA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Yeah, as I understand it you should have 6000 IOPS available for the md
device (ideally).
The iostats you display certainly look benign... but the key time to be
sampling would be when you see the lock list explode - could look very
different then.
Re vm.dirty* - I would crank the values down by a factor of 5:
vm.dirty_background_ratio = 1 (down from 5)
vm.dirty_ratio = 2 (down from 10)
Assuming of course that you actually are seeing an IO stall (which
should be catchable via iostat or iotop)... and not some other issue.
Otherwise leave 'em alone and keep looking :-)
Cheers
Mark
On 02/04/13 13:31, Armand du Plessis wrote:
>
>
> I had a look at the iostat output (on a 5s interval) and pasted it
> below. The utilization and waits seems low. Included a sample below, #1
> taken during normal operation and then when the locks happen it
> basically drops to 0 across the board. My (mis)understanding of the IOPS
> was that it would be 1000 IOPS per/volume and when in RAID0 should give
> me quite a bit higher throughput than in a single EBS volume setup. (My
> naive envelop calculation was #volumes * PIOPS = Effective IOPS :/)
>
>
> I'm looking into vm.dirty_background_ratio, vm.dirty_ratio sysctls. Is
> there any guidance or links available that would be useful as a starting
> point?
>
> Thanks again for the help, I really appreciate it.
>
--
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: mark.kirkwood@catalyst.net.nz, adp@bank.io
Subject: Re: Fwd: Problems with pg_locks explosion
In-Reply-To: <515A5352.4030406@catalyst.net.nz>
* 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