Re: Trying to minimize the impact of checkpoints - Mailing list pgsql-general

From Jan Wieck
Subject Re: Trying to minimize the impact of checkpoints
Date
Msg-id 40CB53EC.5060206@Yahoo.com
Whole thread Raw
In response to Re: Trying to minimize the impact of checkpoints  (Jack Orenstein <jao@geophile.com>)
Responses Re: Trying to minimize the impact of checkpoints
Re: Trying to minimize the impact of checkpoints
List pgsql-general
On 6/12/2004 1:44 PM, Jack Orenstein wrote:

> Jan Wieck wrote:
>> On 6/11/2004 2:02 PM, jao@geophile.com wrote:
>>
>>> Quoting jao@geophile.com:
>>>
>>>> When a checkpoint occurs, all operations slow way, way down.
>>>> The attached spreadsheet (xls file, prepared in OO so unlikely
>>>> to be dangerous) shows a run of a few hours, and the various spikes
>>>> every 25-30 minutes seem consistent with checkpointing. The
>>>> application is doing 1/2 reads and 1/2 inserts during this time.
>>>
>>>
>>> Sorry for being cryptic in my message. The spreadsheet contains
>>> iostat output.
>>
>>
>> Did you try to play with the background writer config options (new in
>> 7.5) at all?
>
> No, not yet. It looks like 7.5 won't be available in time for us to
> use in the first release of our product, so I've been very focused
> on how to best use 7.3-4.
>
> Any opinions on the stability of 7.5 and the effectiveness of the background
> writer in reducing variability in performance due to checkpoints?

I didn't save any of the charts done with 7.4, but the responsetime
spikes on checkpoints went up to 60 seconds without the bgwriter. If you
look at the last chart on this page

     http://developer.postgresql.org/~wieck/vacuum_cost/

there are no spikes at all.


Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


pgsql-general by date:

Previous
From: Steve Atkins
Date:
Subject: Re: Opteron scaling with PostgreSQL
Next
From: jseymour@linxnet.com (Jim Seymour)
Date:
Subject: Re: Opteron scaling with PostgreSQL