[sqlalchemy] Re: How to determine the right number of pooled connections to use

2008-09-19 Thread Alen Ribic
On Sep 19, 5:21 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > On Sep 19, 2008, at 11:16 AM, Alen Ribic wrote: > > if the thread in which the request was served continues to run, not   > serve further requests, and does not clean up after itself, then the   > connections held open local to that

[sqlalchemy] Re: How to determine the right number of pooled connections to use

2008-09-19 Thread Michael Bayer
On Sep 19, 2008, at 11:16 AM, Alen Ribic wrote: > > Michael, thank you for you reply. > Question: if my web request fails to return a response, hence request > method doesn't exit gracefully, could that perhaps cause a connection > not to be returned to a connection pool? Reason I ask this is th

[sqlalchemy] Re: How to determine the right number of pooled connections to use

2008-09-19 Thread Alen Ribic
Michael, thank you for you reply. Question: if my web request fails to return a response, hence request method doesn't exit gracefully, could that perhaps cause a connection not to be returned to a connection pool? Reason I ask this is that if my thinking is right, I might have a clue to exactly w

[sqlalchemy] Re: How to determine the right number of pooled connections to use

2008-09-19 Thread Michael Bayer
On Sep 19, 2008, at 10:05 AM, Alen Ribic wrote: > > Good day. > > I tried to perform a load test on my python web app using sqlalchemy > as follows: > 1000 requests > 20 concurrent connections > > Towards the end, I started getting an error from sqlalchemy module: > TimeoutError: QueuePool limit