pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brad Nicholson <bnichols@ca.afilias.info>
To: pgsql-performance@postgresql.org
Subject: 7.4 Checkpoint Question
Date: Thu, 29 Nov 2007 10:10:54 -0500
Message-ID: <1196349054.5651.19.camel@bnicholson-desktop> (raw)

I have a legacy system still on 7.4 (I know, I know...the upgrade is
coming soon).

I have a fairly big spike happening once a day, every day, at the same
time.  It happens during a checkpoint, no surprise there.  I know the
solution to the problem (upgrade to a modern version), but what I'm
looking for as an explanation as to why one particular checkpoint would
be so bad on a low volume system, so I can appease certain management
concerns. 

This is a _really _low volume system, less than 500 writes/hour.  Normal
operation sees checkpoint related spikes of around 200-300 milliseconds.
We always checkpoint at the checkpoint timeout (every 5 minutes).
During this one checkpoint, I'm seeing transactions running 2-3 seconds.
During this time, writes are < 5/minute.

Relevant settings:
shared_buffers = 10000

checkpoint_segments = 30
checkpoint_timeout = 300

What gives?

-- 
Brad Nicholson  416-673-4106
Database Administrator, Afilias Canada Corp.





view thread (4+ messages)  latest in thread

Message-ID: <1196349054.5651.19.camel@bnicholson-desktop>
Permalink:  ../1196349054.5651.19.camel@bnicholson-desktop/
Also on:    postgresql.org/message-id/1196349054.5651.19.camel@bnicholson-desktop

 · 

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: bnichols@ca.afilias.info
  Subject: Re: 7.4 Checkpoint Question
  In-Reply-To: <1196349054.5651.19.camel@bnicholson-desktop>

* 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