-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boost up postgres #26
base: master
Are you sure you want to change the base?
Conversation
@@ -115,7 +115,7 @@ ssl_key_file = '/etc/ssl/private/ssl-cert-snakeoil.key' | |||
|
|||
# - Memory - | |||
|
|||
shared_buffers = 128MB # min 128kB | |||
shared_buffers = 2GB # min 128kB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is recommended that postgres could get upto 25% of the machine memory.
On staging we are currently at 8GB and 32GB for production, so this change should be safe for both.
@@ -66,7 +66,7 @@ listen_addresses = 'localhost' # what IP address(es) to listen on; | |||
# defaults to 'localhost'; use '*' for all | |||
# (change requires restart) | |||
port = 5432 # (change requires restart) | |||
max_connections = 100 # (change requires restart) | |||
max_connections = 200 # (change requires restart) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure how much this number could rise to. I will get to know when i test things on staging.
As an urgent measure I bumped max_connections to 150 on production. A lot of errors were showing up in celery log, after the recent change to process dataset change async. |
Bumped to 200 on production. |
No description provided.