From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Load distributed checkpoint |
Date: | 2006-12-08 07:13:05 |
Message-ID: | 20061208071305.GG44124@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Thu, Dec 07, 2006 at 10:03:05AM -0600, Kevin Grittner wrote:
> When we first switched our web site to PostgreSQL, this was one of our biggest problems. Queries which normally run in a few milliseconds were hitting the 20 second limit we impose in our web application. These were happening in bursts which suggested that they were caused by checkpoints. 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
Bear in mind that bgwriter settings should be considered in conjunction
with shared_buffer and checkpoint_timeout settings. For example, if you
have 60,000 shared buffers and a 300 second checkpoint interval, those
settings are going to be pretty aggressive.
Generally, I try and configure the all* settings so that you'll get 1
clock-sweep per checkpoint_timeout. It's worked pretty well, but I don't
have any actual tests to back that methodology up.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Filip Rembiałkowski | 2006-12-08 09:28:51 | Re: about PostgreSQL Benchmak( pgbench ) |
Previous Message | Jim C. Nasby | 2006-12-08 06:59:38 | Re: old synchronized scan patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-12-08 10:43:59 | Re: Load distributed checkpoint |
Previous Message | ITAGAKI Takahiro | 2006-12-08 05:49:20 | Re: Load distributed checkpoint |