On Fri, Apr 26, 2013 at 1:52 AM, Michael Bayer <mike...@zzzcomputing.com>wrote:
> > On Apr 25, 2013, at 9:26 PM, Pedro Werneck <pjwern...@gmail.com> wrote: > > > > > > > So, basically it's just passing the eventlet pool as the creator for the > create_engine call? Good. > > > > Right, it isn't critical at all. My system is working perfectly fine and > much faster than without eventlets most of the time, but since I went over > the trouble of changing it to using eventlets, I'd like to try getting the > database connection right too and see if there's any significant > improvemente. > > I did have the thought that if eventlet needs a special connection pool, > you might want to disable SQLAlchemy's own pooling within create_engine() > by passing "poolclass=NullPool". Otherwise it will hold onto a small set > of connections persistently, not sure if that's what eventlet's pool is > trying to implement in a different way. > > That definitely makes sense, but when I set the NullPool while using the eventlet db_pool, I get the whole application stuck after a while, then I get a connection timeout on every thread. I just removed it and using a small SA pool instead, with no problems. Anyway, the eventlet db_pool works beautifully, and increased my throughput significantly. --- Pedro Werneck -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
