From: | Luiz Felipph <luizfelipph(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Optimal configuration for server |
Date: | 2022-03-07 11:51:24 |
Message-ID: | CABCV0czrGy1XfyZ-tXKH=Xts+xo6vvvYnxN4Eb7Q136zYAk9sA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi everybody!
I have a big application running on premise. One of my main database
servers has the following configuration:
72 CPUs(2 chips, 18 physical cores per chip, 2 threads) Xeon Gold 6240
1TB of ram or 786GB (5 servers at all)
A huge storage( I don't know for sure what kind is, but is very powerful)
A consulting company recommended the following configuration for theses
main servers(let me know if something important was left behind):
maxx_connections = 2000
shared_buffers = 32GB
temp_buffers = 1024
max_prepared_transactions = 3000
work_men = 32MB
effective_io_concurrency = 200
max_worker_processes = 24
checkpoint_timeout = 15min
max_wal_size = 64GB
min_wall_size = 2GB
effective_cache_size = 96GB
(...)
I Think this is too low memory setting for de size of server... The number
of connections, I'm still measuring to reduce this value( I think it's too
high for the needs of application, but untill hit a value too high to
justfy any memory issue, I think is not a problem)
My current problem:
under heavyload, i'm getting "connection closed" on the application
level(java-jdbc, jboss ds)
The server never spikes more the 200GB of used ram(that's why I thing the
configuration is too low)
This is the output of free command:
[image: image.png]
Thanks in advance!
Felipph
From | Date | Subject | |
---|---|---|---|
Next Message | Ranier Vilela | 2022-03-07 16:51:35 | Re: Optimal configuration for server |
Previous Message | Ranier Vilela | 2022-03-05 12:08:45 | Re: OOM killer while pg_restore |