Re: Checkpointing question

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "John W Strange" <john(dot)w(dot)strange(at)jpmchase(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Checkpointing question
Date: 2011-02-15 17:51:24
Message-ID: 4D5A68BC020000250003AA8E@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Strange, John W" <john(dot)w(dot)strange(at)jpmchase(dot)com> wrote:

> During heavy writes times we get the checkpoint too often error,
> what's the real knock down effect of checkpointing too often?

The main concern is that it may cause an increase in disk writes,
possibly to the point of causing blocking while waiting for the
disk.

Generally bigger checkpoint_segments settings improve performance,
especially as shared_buffers is increased. There are some
counter-examples, particularly during bulk loads, which haven't
really been explained:

http://archives.postgresql.org/pgsql-hackers/2010-04/msg00848.php

That makes this an area where careful testing of your real workload
with different settings can be important, at least if you're trying
to wring that last ounce of performance out of your server..

-Kevin

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2011-02-15 18:01:53 Re: high user cpu, massive SELECTs, no io waiting problem
Previous Message Thomas Pöhler 2011-02-15 17:19:14 high user cpu, massive SELECTs, no io waiting problem