Changes
Jump to navigation
Jump to search
checkpoint_segments=32
This is equivalent to every 512Mb
#In KB, so 1024 * 512=> 524288 = 512Mb, Note that this might be a little too high for aggresively stacked queries But this seems to be the bite point for performance. (kranthi: may not do much after some limit, max allowed 2GB)
(#786432 => 6 * 1073741824 => 6 * 131072 * 8 * 1024 This is how much VACUUM will use - it doesn't make a huge difference)
#In 8k blocks. This is the maximum memory that postgres will allocate.
It is currently set to 14Gb.
Database Server Documentation (view source)
Revision as of 14:24, 17 March 2016
, 14:24, 17 March 2016→Adding a dbase user and creating a dbase
port = 5432
max_connections = 10
shared_buffers = 100000 MB(~40% of 264 GB)
The recommendation is to use around 25-40% of RAM (we have 256Gb) for high-performance systems like ours. We might need to check that we are running 64bit and that our kernel supports this.
work_mem = 500MB
maintenance_work_mem = 2GB
effective_cache_size = 198GB(-3/4 of the current RAM)
Restart postgres to reload the configuration:
/etc/init.d/postgresql restart
==McNair Center Users==
