On Dec 12, 2012, at 9:33 PM, Jaimy Azle wrote: > Previously, I use SQLA 0.7.2 on Jython for production and it works > great for almost one year deployment until recently I manage to > upgrade to 0.7.8. With this new version, I noticed a constant > performance degradation mostly after serveral hours running, > eventually overall system become almost unusable when a single query > takes almost 10 second to complete. I have not examine in detail > however, but temporarily revert the upgrade back to 0.7.2 to let the > everything works. > > As this still a preliminary issue to me, anybody here ever notice the > same problem? or is there any clue before i put some effort in > examining this? Had tried to google but found nothing. I use SQLA as > our ORM backbone in a middleware server running on Java. > > Almost nothing changed when we were upgrading SQLA except for Jython > which should be upgraded from 2.5.2 to 2.5.3 to fix SQLA import > problem. Other technology stack used:
This is nothing anyone has reported. Jython though has frequent issues in my observation, that SQLAlchemy often tends to collide with. You'd want to try to bisect to figure out exactly which SQLAlchemy version, and also try using pdb to figure out what's happening in these slow situations, though that might be challenging as you'd need to isolate a test case that can reproduce the slowness. -- 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.
