Re: Auto-tuning work_mem and maintenance_work_mem
| От | Jeff Janes |
|---|---|
| Тема | Re: Auto-tuning work_mem and maintenance_work_mem |
| Дата | |
| Msg-id | CAMkU=1yzdOCFaYT80CTNuWuZJEjojr7eO9e_jtyKo6aP_UakFA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Auto-tuning work_mem and maintenance_work_mem ("Joshua D. Drake" <jd@commandprompt.com>) |
| Ответы |
Re: Auto-tuning work_mem and maintenance_work_mem
|
| Список | pgsql-hackers |
On Thu, Oct 17, 2013 at 9:03 AM, Joshua D. Drake <jd@commandprompt.com> wrote:
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.
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?
Why don't we just have 3 default config files:
2GB memory
4GB memory
8GB memory
But what would go in each of those files? Once we agree on what would be in them, why not just have a continuous knob that does that same thing?
Would your suggestion for the 2GB file have work_mem be at least 4 MB?
Cheers,
Jeff
В списке pgsql-hackers по дате отправления: