Re: Configuring PostgreSQL to minimize impact of checkpoints

From: Jack Orenstein <jao(at)geophile(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
Date: 2004-05-11 02:02:29
Message-ID: 40A03435.7020300@geophile.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Bruce Momjian wrote:
> jao(at)geophile(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Bruce Momjian 2004-05-11 02:33:27 Re: Configuring PostgreSQL to minimize impact of checkpoints
Previous Message Bricklen 2004-05-10 20:37:22 Re: Help how to tune-up my Database