| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | 'Alexey Vasiliev' <leopard_ne(at)inbox(dot)ru> |
| Cc: | 'Josh Berkus' <josh(at)agliodbs(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: pgtune + configurations with 9.3 |
| Date: | 2014-11-14 17:06:54 |
| Message-ID: | 0683F5F5A5C7FE419A752A034B4A0B9797DCD4DA@sswchi5pmbx2.peak6.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Alexey,
The issue is not that 8GB is the maximum. You *can* set it higher. What I'm saying, and I'm not alone in this, is that setting it higher can actually decrease performance for various reasons. Setting it to 25% of memory on a system with 512GB of RAM for instance, would be tantamount to disaster. A checkpoint with a setting that high could overwhelm pretty much any disk controller and end up completely ruining DB performance. And that's just *one* of the drawbacks.
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey Vasiliev | 2014-11-14 19:10:24 | Re[2]: [PERFORM] pgtune + configurations with 9.3 |
| Previous Message | Alexey Vasiliev | 2014-11-14 16:40:19 | [PERFORM] pgtune + configurations with 9.3 |