From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Joe Conway <mail(at)joeconway(dot)com>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Excessive WAL generation and related performance issue |
Date: | 2014-04-14 23:17:29 |
Message-ID: | 3627.1397517449@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-04-14 14:33:03 -0700, Joe Conway wrote:
>> checkpoint_segments = 96
>> checkpoint_timeout = 10min
> I bet you'll see noticeably - while still not great - better performance
> by setting checkpoint_timeout to an hour (with a corresponding increase
> in checkpoint_segments).
> Have you checked how often checkpoints are actually created? I'd bet
> it's far more frequent than every 10min with that _segments setting and
> such a load.
My thoughts exactly. It's not hard to blow through WAL at multiple
megabytes per second with modern machines. I'd turn on checkpoint logging
and then do whatever you need to do to get the actual intercheckpoint time
up to 10-15 minutes at least.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2014-04-14 23:22:48 | Re: Excessive WAL generation and related performance issue |
Previous Message | Michael Paquier | 2014-04-14 23:11:05 | Re: Including replication slot data in base backups |