| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-performance(at)lists(dot)postgresql(dot)org, aditya desai <admad123(at)gmail(dot)com>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Selecting RAM and CPU based on max_connections |
| Date: | 2022-05-20 10:15:47 |
| Message-ID: | B6D783EC-C01A-41D2-BF6E-896A8273D7DD@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 20 May 2022 10:27:50 CEST, aditya desai <admad123(at)gmail(dot)com> wrote:
>Hi,
>One of our applications needs 3000 max_connections to the database.
>Connection pooler like pgbouncer or pgpool is not certified within the
>organization yet. So they are looking for setting up high configuration
>Hardware with CPU and Memory. Can someone advise how much memory and CPU
>they will need if they want max_conenction value=3000.
>
>Regards,
>Aditya.
Pgbouncer would be the best solution. CPU: number of concurrent connections. RAM: shared_buffer + max_connections * work_mem + maintenance_mem + operating system + ...
--
2ndQuadrant - The PostgreSQL Support Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-05-20 10:31:35 | Re: Selecting RAM and CPU based on max_connections |
| Previous Message | aditya desai | 2022-05-20 08:27:50 | Selecting RAM and CPU based on max_connections |