@lisandro: michele is right.. the pool_size parameter calculation are accurate only if there's one process per app. web2py can't coordinate pools among different processes... also, max_client_conn is exactly the maximum number of connection the pgbouncer process will allow "coming in". Once over the max, others will be queued. What pgbouncer does is exactly what web2py does if it runs in a single process and with a single DAL connection: it keeps n connections open to the backend and recycles connections coming in. Once "full", the latest coming in needs to wait for a connection to be freed.
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
