| From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | Jarek <jarek(at)poczta(dot)srv(dot)pl>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Big number of connections |
| Date: | 2016-03-31 19:12:44 |
| Message-ID: | DM2PR07MB557C8C149398C16068654A2DA990@DM2PR07MB557.namprd07.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
-----Original Message-----
From: pgsql-performance-owner(at)postgresql(dot)org [mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of Jarek
Sent: Thursday, March 31, 2016 3:08 PM
To: pgsql-performance(at)postgresql(dot)org
Subject: [PERFORM] Big number of connections
Hello!
We are going to build system based on PostgreSQL database for huge number of individual users (few thousands). Each user will have his own account, for authorization we will use Kerberos (MIT or Windows).
Most of users will have low activity, but for various reasons, connection should be open all the time.
I'd like to know what potential problems and limitations we can expect with such deployment.
During preliminary testing we have found that for each connection we need ~1MB RAM. Is there any way to decrease this ? Is there any risk, that such number of users will degrade performance ?
I'll be happy to hear any remarks and suggestions related to design, administration and handling of such installation.
best regards
Jarek
_______________________________________________________________________________
Take a look at PgBouncer.
It should solve your problems.
Regards,
Igor Neyman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2016-03-31 19:51:23 | Re: Big number of connections |
| Previous Message | Jarek | 2016-03-31 19:08:06 | Big number of connections |