Re: Load distributed checkpoint - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Re: Load distributed checkpoint
Date
Msg-id 20061208142419.665B.ITAGAKI.TAKAHIRO@oss.ntt.co.jp
Whole thread Raw
In response to Re: Load distributed checkpoint  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote:

> We adjusted the background writer configuration and nearly eliminated
> the problem.
>  
>  bgwriter_all_maxpages           | 600
>  bgwriter_all_percent            | 10
>  bgwriter_delay                  | 200
>  bgwriter_lru_maxpages           | 200
>  bgwriter_lru_percent            | 20
>  
> Between the xfs caching and the batter backed cache in the RAID
> controller, the disk writes seemed to settle out pretty well.

Yes, higher bgwriter_all_maxpages is better for stability. I also do so
up to now. However, if some processes makes lots of dirty buffers in the
shortest time, ex.VACUUM, bgwriter begins to write many pages and affects
responce time.

We will be able to set bgwriter_all_maxpages to lower value with load
distributed checkpoint. It expands the range of tuning of bgwriter.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Gavin Sherry
Date:
Subject: Re: Weak passwords and brute force attacks
Next
From: "Pavel Stehule"
Date:
Subject: Re: SQL/PSM implemenation for PostgreSQL (roadmap)