|
Here is some more information pool_mode | transaction We have transactional pooling and our application is set up in such a way that we have one query per transaction. We have set default pool size to 100.
This is output . As you guys can see active connection are 100 and 224 are waiting. We are planning to move default pool size to 250. Please suggest if you guys think otherwise pgbouncer=# show pools; database | user | cl_active | cl_waiting | sv_active | sv_idle | sv_used | sv_tested | sv_login | maxwait -----------+-----------+-----------+------------+-----------+---------+---------+-----------+----------+--------- pgbouncer | pgbouncer | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 site | feature | 418 | 0 | 20 | 17 | 0 | 0 | 0 | 0 site | service | 621 | 224 | 100 | 0 | 0 | 0 | 0 | 0 site | zabbix | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 Prabhjot Singh Database Administrator CLASSMATES 1501 4th Ave., Suite 400 Seattle, WA 98101 206.301.4937 o 206.301.5701 f From: Sheena, Prabhjot Guys we see spike in pg bouncer during the peak hours and that was slowing down the application. We did bump up the connection limit and it is helpful but now we again notice little spike in connection. And one thing that I notice that
is different is jump in sv_used value when I run command show pools during problem times
Can anyone please explain what value of sv_used means when i run show pools;
Prabhjot
|
