Difference between revisions of "Tuning the PostgreSQL Database"
From Observer GigaFlow Support | VIAVI Solutions Inc.
Kevin Wilkie (Talk | contribs) |
Kevin Wilkie (Talk | contribs) |
||
| Line 4: | Line 4: | ||
shared_buffers='''1/4 of the available memory''' | shared_buffers='''1/4 of the available memory''' | ||
| + | |||
effective_cache_size = '''1/2 of available memory''' | effective_cache_size = '''1/2 of available memory''' | ||
| Line 12: | Line 13: | ||
log_min_duration_statement = 5000 | log_min_duration_statement = 5000 | ||
synchronous_commit = off | synchronous_commit = off | ||
| − | work_mem = | + | work_mem = 10MB |
wal_buffers= 10MB | wal_buffers= 10MB | ||
commit_delay 10 | commit_delay 10 | ||
max_locks_per_transaction=3000 | max_locks_per_transaction=3000 | ||
| − | |||
| − | + | ||
| − | effective_cache_size = | + | Example for a server with 16GB of RAM |
| − | shared_buffers = | + | effective_cache_size = 8GB |
| + | shared_buffers = 4000MB | ||
Revision as of 08:38, 13 October 2016
Tuning of postgres is done via the postgresql.conf file.
Settings based on available RAM
shared_buffers=1/4 of the available memory
effective_cache_size = 1/2 of available memory
Standard Settings
autovacuum_max_workers = 1 checkpoint_completion_target = 0.9 checkpoint_segments = 32 log_min_duration_statement = 5000 synchronous_commit = off work_mem = 10MB wal_buffers= 10MB commit_delay 10 max_locks_per_transaction=3000
Example for a server with 16GB of RAM
effective_cache_size = 8GB shared_buffers = 4000MB
