> -----Original Message----- > From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general- > owner@xxxxxxxxxxxxxx] On Behalf Of Thomas Kellerer > Sent: Tuesday, September 25, 2012 5:25 PM > To: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: idle in transaction query makes server unresponsive > > Scot Kreienkamp wrote on 25.09.2012 22:35: > > The application is using a pooler and generally runs around 100 > > connections, but I've seen it as high as 200 during the day for > > normal use. It's on a large server; 64 cores total and about 500 > > gigs of memory. That's one of the reasons I left it at 512 > > connections. > > We had several web applications where performance was *improved* > by configuring the connection pool have a a lot less connections. > > There is a threshold where too many connections > will simply flood the server. Lowering the number of processes > fighting for resource makes each process faster. > > You might want to give it a try. > [Scot Kreienkamp] Can I get the same effect by limiting the number of logons for the user that my application is connecting as to 250? Or do I need to lower the number in postgresql.conf? I'd rather go with the first option because I can adjust it live without editing and reloading config files. This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
