Re: Automatic adjustment of bgwriter_lru_maxpages
| От | Jim C. Nasby |
|---|---|
| Тема | Re: Automatic adjustment of bgwriter_lru_maxpages |
| Дата | |
| Msg-id | 20070516000807.GF20707@nasby.net обсуждение исходный текст |
| Ответ на | Re: Automatic adjustment of bgwriter_lru_maxpages (daveg <daveg@sonic.net>) |
| Список | pgsql-patches |
Moving to -performance. On Mon, May 14, 2007 at 09:55:16PM -0700, daveg wrote: > Apologies for asking this on the wrong list, but it is at least the right > thread. > > What is the current thinking on bg_writer setttings for systems such as > 4 core Opteron with 16GB or 32GB of memory and heavy batch workloads? It depends greatly on how much of your data tends to stay 'pinned' in shared_buffers between checkpoints. In a case where the same data tends to stay resident you're going to need to depend on the 'all' scan to decrease the impact of checkpoints (though the load distributed checkpoint patch will change that greatly). Other than that tuning bgwriter boils down to your IO capability as well as how often you're checkpointing. -- Jim Nasby decibel@decibel.org EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
В списке pgsql-patches по дате отправления: