Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
| От | Magnus Hagander |
|---|---|
| Тема | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |
| Дата | |
| Msg-id | CABUevEzkWHmk3D45ap2_2kR-MfvJ2Q-YwEnD_AfvF8zdB0au9g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers (Andres Freund <andres@2ndQuadrant.com>) |
| Список | pgsql-hackers |
On Wed, May 7, 2014 at 4:12 PM, Andres Freund <andres@2ndquadrant.com> wrote:
If we can't make the autotuning better than that, we're better off holding off on that one until we can actually figure out something better. (At which point perhaps we can reach the level where we can just remove it.. But that's all handwaving about the future of course).
On 2014-05-07 10:07:07 -0400, Tom Lane wrote:+1 for increasing it to 4GB and remove the autotuning. I don't like the
> In the meantime, it seems like there is an emerging consensus that nobody
> much likes the existing auto-tuning behavior for effective_cache_size,
> and that we should revert that in favor of just increasing the fixed
> default value significantly. I see no problem with a value of say 4GB;
> that's very unlikely to be worse than the pre-9.4 default (128MB) on any
> modern machine.
>
> Votes for or against?
current integration into guc.c much and a new static default doesn't
seem to be worse than the current autotuning.
+1.
If we can't make the autotuning better than that, we're better off holding off on that one until we can actually figure out something better. (At which point perhaps we can reach the level where we can just remove it.. But that's all handwaving about the future of course).
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: