From: | Oliver Jagape <oliver(dot)jagape(at)concentrix(dot)com> |
---|---|
To: | bricklen <bricklen(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Ideal configuration for postgresql 9.3 config |
Date: | 2016-02-19 06:59:12 |
Message-ID: | BLUPR07MB9641209B073AB57C4EC7D6395A00@BLUPR07MB964.namprd07.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks for the reply,
I tried some of suggested changes and some are modified based on this Link I stumbled on the web..
Though I'll be able to observe the outcome on the next few days when most of the users will rush on using the apps that depend on this db.
Regards,
Oliver
________________________________
From: bricklen <bricklen(at)gmail(dot)com>
Sent: Wednesday, February 17, 2016 12:59 PM
To: Oliver Jagape
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Ideal configuration for postgresql 9.3 config
Hi Oliver,
I have suggested a few changes below.
On Tue, Feb 16, 2016 at 7:15 PM, Oliver Jagape <oliver(dot)jagape(at)concentrix(dot)com<mailto:oliver(dot)jagape(at)concentrix(dot)com>> wrote:
CPU: 16 cores
RAM: 48GB
Disk for Data is at a fiber channel SAN storage.
max_connections = 1024
If you need that many concurrent connections, invest in a connection pooler. If no connection pooler is used, knock off 800 connections if you can.
shared_buffers = 8000MB
Test with a lower setting like 4GB, depending on your workload, that may or may not perform better.
work_mem = 4096MB
This magnitudes too high. It is per query * sort and aggregation steps. If you expect queries with large result sets (or distinct, group by, etc), 100MB is probably a reasonable starting point.
maintenance_work_mem = 512MB
Depending on your relation size, you might want to double this.
checkpoint_segments = 512
Is that a reason you chose such a high number?
enable_nestloop = off
Unless you have a clear reason to disable this (it applies to all queries), leave this enabled.
autovacuum = off
autovacuum should be on unless you know your data churn patterns and have scheduled manual vacuums.
autovacuum_naptime = 60
You probably want that more aggressive, like 5s.
From | Date | Subject | |
---|---|---|---|
Next Message | nunks | 2016-02-19 11:48:36 | Re: ANALYZE'ing table hierarchies |
Previous Message | gaoqiangdba@163.com | 2016-02-19 06:41:43 | Re: ANALYZE'ing table hierarchies |