now the question is , is it possible to dig out from from postgresql database
server if connection pooling is needed ? In our case eg i have kept
max_connections = 300 if i reduce below 250 i get error "max connection reached....."
on connecting to db directly, if i put pgbouncer i get less performance
(even if no clients waiting)
without pooling the dbserver CPU usage increases but performance of apps
is also become good.
Regds
Rajesh Kumar Mallah.
On Sun, Jul 18, 2010 at 10:55 PM, Greg Smith <greg@xxxxxxxxxxxxxxx> wrote:
Rajesh Kumar Mallah wrote:Of course pgbouncer is going decrease performance in this situation. You've added a whole layer to things that all traffic has to pass through, without a setup that gains any benefit from the connection pooling. Try making the client count 1000 instead if you want a useful test.
the no of clients was 10 ( -c 10) carrying out 10000 transactions each (-t 10000) .
pgbench db was initilised with scaling factor -s 100.
since client count was less there was no queuing of requests in pgbouncer
i would prefer to say it was in 'passthrough' mode.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@xxxxxxxxxxxxxxx www.2ndQuadrant.us
