From: Tom Lane <tgl@sss.pgh.pa.us>
To: Elanchezhiyan Elango <elanelango@gmail.com>
Cc: Tomas Vondra <tv@fuzzy.cz>
Cc: pgsql-performance@postgresql.org
Subject: Re: Checkpoints and slow queries
Date: Mon, 28 Apr 2014 10:07:37 -0400
Message-ID: <10039.1398694057@sss.pgh.pa.us> (raw)
In-Reply-To: <CALqA5kgoni52uqsSDeZStXZReXdpzGtSQ8iTtHbmx5oKOb1G6Q@mail.gmail.com>
References: <CALqA5kjzDQ2X1Am5zNjg3R5vCmZD-D0_6nrO1ccVD8vOmej22g@mail.gmail.com>
<535D88B6.5090002@fuzzy.cz>
<CALqA5kgoni52uqsSDeZStXZReXdpzGtSQ8iTtHbmx5oKOb1G6Q@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Elanchezhiyan Elango <elanelango@gmail.com> writes:
>> The problem is that while this makes the checkpoints less frequent, it
>> accumulates more changes that need to be written to disk during the
>> checkpoint. Which means the impact more severe.
> True. But the checkpoints finish in approximately 5-10 minutes every time
> (even with checkpoint_completion_target of 0.9).
There's something wrong with that. I wonder whether you need to kick
checkpoint_segments up some more to keep the checkpoint from being run
too fast.
Even so, though, a checkpoint spread over 5-10 minutes ought to provide
the kernel with enough breathing room to flush things. It sounds like
the kernel is just sitting on the dirty buffers until it gets hit with
fsyncs, and then it's dumping them as fast as it can. So you need some
more work on tuning the kernel parameters.
regards, tom lane
--
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: tgl@sss.pgh.pa.us, elanelango@gmail.com, tv@fuzzy.cz
Subject: Re: Checkpoints and slow queries
In-Reply-To: <10039.1398694057@sss.pgh.pa.us>
* 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