On Wed, Mar 26, 2014 at 5:14 PM, Shaun Thomas <sthomas@xxxxxxxxxxxxxxxx> wrote: > * Checkpoints must commit dirty shared buffers to disk. The larger this is, the more risk you have when checkpoints come, up to and including an unresponsive database. Writing to disks isn't free, and sadly this is still on the slower side unless all of your storage is SSD-based. You don't want to set this too much higher than your disk write cache. We use on some heavy working machines 48GB of shared buffers (and sometimes more - depends on amount of RAM). Of course that works only with good enough hardware raid with large bbu, well tuned linux (dirty bytes appropriate to raid cache size etc) and aggressively tuned both checkpoints and background writer: bgwriter_delay | 10 bgwriter_lru_maxpages | 1000 bgwriter_lru_multiplier | 10 checkpoint_completion_target | 0.9 checkpoint_segments | 300 checkpoint_timeout | 3600 and it really makes sense -- Ilya Kosmodemiansky, PostgreSQL-Consulting.com tel. +14084142500 cell. +4915144336040 ik@xxxxxxxxxxxxxxxxxxxxxxxxx -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
