| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |
| Date: | 2013-09-10 22:08:24 |
| Message-ID: | 522F9858.7000008@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin,
> I vote 4x on the basis that for this setting (unlike almost all the
> other memory settings) the ramifications for setting it too high
> generally aren't too bad. Also, the o/s and temporary memory usage as
> a share of total physical memory has been declining over time
If we're doing that, then we should change our general advice on this
setting as well.
Another argument in favor: this is a default setting, and by default,
shared_buffers won't be 25% of RAM.
> (meaning, that if you have a 256gb memory server and follow the advice
> to set to 64gb, your memory for caching is approximately 64gb).
Wait, what?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2013-09-10 22:21:48 | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |
| Previous Message | David Fetter | 2013-09-10 21:56:41 | 9.4 CommitFest 2 Starts Sunday 15 September 2013! |