Gloria wrote: > > OK, so is the solution to run these in separate processes instead? > Is this a GIL limitation?
not at all. you would need to a. determine that you do in fact have queries that are taking exceedingly long to complete and then b. repair those queries so that they return in a reasonable amount of time. One thing that might help here is to enable python logging, using a formatter that includes the current thread id. then enable "sqlalchemy.pool" logging which will indicate which threads are checking out connections at what time. If you can additionally enable logging in your application that illustrates request URLs coming in and responses completing, you can match up those requests with pool activity via the thread id. you'll have a crystal clear picture of what threads/requests are checking out how many connections, and when/if they are being returned to the pool. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
