"Gnanakumar" <gnanam@xxxxxxxxxx> wrote: > our web-based application has crossed more than 500 concurrent > users. Hence we've already upgraded RAM and now we want to > upgrade max connection parameter too. Yes, we're already using > pgpool-II v3.1.1 for connection pooling. The main point of using a connection pooler is to funnel a large number of client connection into the pooler into a small number of database connections. We get very good performance dealing with thousands of concurrent users with a pool of 35 connections to the database. We originally had a larger pool, but contention was reducing performance, and we found that throughput and latency both improved with a smaller pool of database connections. If you want to handle more users than you can currently support, you probably need to use fewer database connections. -Kevin -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
