| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: need help on memory allocation |
| Date: | 2018-01-23 14:08:07 |
| Message-ID: | c3781bdb-737d-4f08-1b0f-f066d71dd231@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Am 23.01.2018 um 14:59 schrieb Rambabu V:
> total used free shared buffers cached
> Mem: 58G 58G 358M 16G 3.6M 41G
> -/+ buffers/cache: 16G 42G
> Swap: 9.5G 687M 8.9G
>
> *postgresql.conf parametes:*
> *=====================*
> work_mem = 256MB# min 64kB
> maintenance_work_mem = 256MB# min 1MB
> shared_buffers = 16GB# min 128kB
> temp_buffers = 16MB# min 800kB
> wal_buffers = 64MB
> effective_cache_size = 64GB
> max_connections = 600
>
how many active concurrent connections do you have? With work_mem =
256MB and 600 active connections and only 1 allocation of work_mem per
connection you will need more than 150GB of RAM.
With other words: you should lowering work_mem and/or max_connections.
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Marc Lessard | 2018-01-23 14:08:17 | RE: Inefficient full seq scan on pg_largeobject instead of index scan |
| Previous Message | Rambabu V | 2018-01-23 13:59:31 | Re: need help on memory allocation |