From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Shane Wright <me(at)shanewright(dot)co(dot)uk> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: hanging for 30sec when checkpointing |
Date: | 2004-02-03 23:44:18 |
Message-ID: | 3020.1075851858@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Shane Wright <me(at)shanewright(dot)co(dot)uk> writes:
> When the db is under medium-heavy load, it periodically spawns a
> 'checkpoint subprocess' which runs for between 15 seconds and a minute.
It sounds like checkpoint is saturating your disk bandwidth.
> I've looked at the documentation and various bits about adjusting
> checkpoint segments and timings - but it seems reducing segments/timeout
> is implied to be bad, but it seems to me that increasing either will
> just make the same thing happen less often but more severely.
I was actually just about to suggest reducing the inter-checkpoint
interval. That should reduce the volume of data that needs to be
written per checkpoint. Might spread the pain a little thinner at least.
If you think you should have more disk bandwidth available than the
system seems to be using, maybe there is something wrong with the disk
or kernel configuration, but that's way out of my league to diagnose.
You'd probably need to find some kernel hackers to help you with that.
BTW, Jan Wieck has been doing some work recently to try to reduce the
"I/O storm at checkpoint" effect, but it won't appear till 7.5.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Iain | 2004-02-04 01:40:31 | Re: hanging for 30sec when checkpointing |
Previous Message | Shane Wright | 2004-02-03 22:35:02 | hanging for 30sec when checkpointing |