Difference between revisions of "Tuning the PostgreSQL Database"
From Observer GigaFlow Support | VIAVI Solutions Inc.
Kevin Wilkie (Talk | contribs) |
Kevin Wilkie (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | Tuning of postgres is done via the postgresql.conf file | + | 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''' | effective_cache_size = '''1/2 of available memory''' | ||
| + | '''Standard Settings''' | ||
autovacuum_max_workers = 1 | autovacuum_max_workers = 1 | ||
checkpoint_completion_target = 0.9 | checkpoint_completion_target = 0.9 | ||
Revision as of 08:37, 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 = 4MB wal_buffers= 10MB commit_delay 10 max_locks_per_transaction=3000 work_mem=4
For 2GB system
effective_cache_size = 1GB shared_buffers = 500MB
