Re: Setting up a database for 10000 concurrent users - Mailing list pgsql-general

From Melvin Davidson
Subject Re: Setting up a database for 10000 concurrent users
Date
Msg-id CANu8FiwmP=dZzsVzUSouNt2JtSmnGRL_ubzGMZ4ZnGNi50Syrg@mail.gmail.com
Whole thread Raw
In response to Re: Setting up a database for 10000 concurrent users  (Andy Colson <andy@squeakycode.net>)
Responses Re: Setting up a database for 10000 concurrent users
List pgsql-general
I suggest pg_bouncer as opposed to pg_pool. My testing showed it handled connections better. Ultimately the choice is yours, but with 10000 connections, you absolutely need a connection manger.

On Mon, May 4, 2015 at 10:08 AM, Andy Colson <andy@squeakycode.net> wrote:
On 05/04/2015 02:02 AM, sanjeetkamble wrote:
Hello,

Please let me know how The database server is started with max_connections =
10000 ???

I have same issue, but i have a SAN storage where Postgresql  is installed.


Sanjeet



No doubt that would be a problem.  Its bad idea.  set max_connections to core count * 2, then put pg_pool in front, and set pg_pools max count to 10000.

-Andy




--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: Andy Colson
Date:
Subject: Re: Setting up a database for 10000 concurrent users
Next
From: Andy Colson
Date:
Subject: Re: Setting up a database for 10000 concurrent users