Thank you, Mike! What you say makes sense, and I took this question into the Pylons group <https://groups.google.com/forum/#!topic/pylons-discuss/D331k45foFA> to get their views and recommendations. (Unfortunately I have no control over the number of subrequests, and thus connections, as that’s a result of user’s request data.)
Jens On Thursday, April 26, 2018 at 11:10:03 PM UTC+10, Mike Bayer wrote: > > I'm not familiar with this concept but it seems to me that your web > server can have at most N concurrent requests and that there would > need to be some system that also sets a limit on the number of > subrequests. If you are planning to have thousands of concurrent > subrequests at a time and you'd like them to all use independent > database connections then you'd need to configure your pool to allow > thousands of overflow connections, however, now you need to look at > how many processes you will be running and how many connections your > database itself allows. > > The point is that there are hard limits on how many connections you > can have to your database, which is a good thing. Any system that > generates lots of database connections similarly needs to work within > these limits, so you'd need to plan for this. > -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
