Re: Auto-tuning work_mem and maintenance_work_mem

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: Auto-tuning work_mem and maintenance_work_mem
Дата
Msg-id CAMkU=1wfbW77Xg2Ft0b14wjrfEK=rkB0N1=xMJjfZZmGgZTErQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Auto-tuning work_mem and maintenance_work_mem  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Дерево обсуждения
On Sun, Feb 16, 2014 at 6:26 PM, Robert Haas <robertmhaas@gmail.com> wrote:

 
The current bgwriter_lru_maxpages value limits the background writer
to a maximum of 4MB/s.  If one imagines shared_buffers = 8GB, that
starts to seem rather low, but I don't have a good feeling for what a
better value would be.

I don't quite understand the point of bgwriter_lru_maxpages in the first place.  What is it supposed to protect us from?

I wonder if that isn't an artefact from when the checkpointer was the same process as the background writer, to prevent the background writer functionality from starving the checkpointer functionality.


Cheers,

Jeff

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster