Re: Auto-tuning work_mem and maintenance_work_mem - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Auto-tuning work_mem and maintenance_work_mem
Date
Msg-id 52600A35.5060907@commandprompt.com
Whole thread Raw
In response to Re: Auto-tuning work_mem and maintenance_work_mem  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: Auto-tuning work_mem and maintenance_work_mem  (Robert Haas <robertmhaas@gmail.com>)
Re: Auto-tuning work_mem and maintenance_work_mem  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On 10/17/2013 08:55 AM, Kevin Grittner wrote:
>
> Robert Haas <robertmhaas@gmail.com> wrote:
>
>> I still think my previous proposal of increasing the defaults for
>> work_mem and maintenance_work_mem by 4X would serve many more
>> people well than it would serve poorly.  I haven't heard anyone
>> disagree with that notion.  Does anyone disagree?  Should we do
>> it?
>
> I think that it makes sense to do that.  Those are still reasonable
> defaults for a machine with 2GB of RAM, maybe even with less.
> We're talking about putting this only in a release that will come
> out in 2014.  How many machines used for a database server that new
> will have less than that?

A lot. A whole lot, more than what most people have in production with 
more than that. You are forgetting a very large segment of the 
population who run... VMs.

Why don't we just have 3 default config files:

2GB memory
4GB memory
8GB memory

Have initdb detect how much memory is available on the machine in TOTAL 
and pick the most appropriate.

Joshua D. Drake


-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms   a rose in the deeps of my heart. - W.B. Yeats



pgsql-hackers by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: Auto-tuning work_mem and maintenance_work_mem
Next
From: Noah Misch
Date:
Subject: Re: space reserved for WAL record does not match what was written: panic on windows