Re: Auto-tuning work_mem and maintenance_work_mem

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Auto-tuning work_mem and maintenance_work_mem
Дата
Msg-id 20131016203056.GF18048@momjian.us
обсуждение исходный текст
Ответ на Re: Auto-tuning work_mem and maintenance_work_mem  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: Auto-tuning work_mem and maintenance_work_mem  (Claudio Freire <klaussfreire@gmail.com>)
Список pgsql-hackers
On Wed, Oct 16, 2013 at 04:25:37PM -0400, Andrew Dunstan wrote:
> 
> On 10/09/2013 11:06 AM, Andrew Dunstan wrote:
> >
> >
> >
> >The assumption that each connection won't use lots of work_mem is
> >also false, I think, especially in these days of connection
> >poolers.
> >
> >
> 
> 
> Andres has just been politely pointing out to me that my knowledge
> of memory allocators is a little out of date (i.e. by a decade or
> two), and that this memory is not in fact likely to be held for a
> long time, at least on most modern systems. That undermines
> completely my reasoning above.
> 
> Given that, it probably makes sense for us to be rather more liberal
> in setting work_mem that I was suggesting.

Ah, yes, this came up last year (MMAP_THRESHOLD):
http://www.postgresql.org/message-id/20120730161416.GB10877@momjian.us

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: Auto-tuning work_mem and maintenance_work_mem
Следующее
От: Kevin Grittner
Дата:
Сообщение: Re: [PATCH] pg_sleep(interval)