From: Jack Orenstein <jao@geophile.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
Date: Mon, 10 May 2004 22:02:29 -0400
Message-ID: <40A03435.7020300@geophile.com> (raw)
In-Reply-To: <200405101909.i4AJ9Wv09415@candle.pha.pa.us>
References: <200405101909.i4AJ9Wv09415@candle.pha.pa.us>
Bruce Momjian wrote:
> jao@geophile.com wrote:
>
>>4. I understand that a "background writer" is being contemplated for
>>7.5. Will that replace or augment the checkpoint process? Any
>>comments on how that work will apply to my problem would be
>>appreciated. I wouldn't mind seeing the average performance,
>>(without the spikes) go up -- let's say -- 10%, in exchange for
>>more uniform performance. These spikes are a real problem.
>
>
> The background writer is designed to address your specific problem. We
> will stil checkpoint, but the spike should be greatly minimized.
>
Thanks. Do you know when 7.5 is expected to be released?
Until then, is a workaround known? Also, are the delays I'm seeing out of the ordinary?
I'm looking at one case in which two successive transactions, each updating a handful of
records, take 26 and 18 *seconds* (not msec) to complete. These transactions normally complete
in under 30 msec.
Jack Orenstein
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: jao@geophile.com, pgman@candle.pha.pa.us
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
In-Reply-To: <40A03435.7020300@geophile.com>
* 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