Each process of your application will open up to 15 connections (5 + 10 for momentary bursts) to the DB Server and will close them when "pool_recycle" timeout triggers.
On Fri, Dec 2, 2011 at 2:25 PM, NiL <[email protected]> wrote: > Hi list, > > in apache conf I have > > WSGIDaemonProcess myapp threads=10 processes=20 display-name=%{GROUP} > > in myapp/config/app_cfg.py > > I don't have anything specific so > > class QueuePool(Pool): > """A Pool that imposes a limit on the number of open connections.""" > > def __init__(self, creator, pool_size=5, max_overflow=10, timeout=30, > **kw): > > applies. I read in sqla's strategies that this is the default > > when I stress the app with jmeter (250 connections on 30 seconds), I quickly > have > > OperationalError: (OperationalError) FATAL: too many clients already > connected > > in apache/error.log and that comes from Postgres. > (in postgres.conf max_connections is 200) > > So what I'd like to understand is how to evaluate the max number of > connection that my app will open to the dbms > > tx > > NIL > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/turbogears/-/eCA4NILT94EJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
