That's cool. I made some tests with a "GeventReactor" with SQLAlchemy
and the psycopg "green" implementation. The results were ~20% faster in
almost all benchs I made, but I didn't tested them in production yet.
On 06/12/2013 05:48 PM, Michael Bayer wrote:
I'm looking forward to Pep3156
(http:
I'm looking forward to Pep3156 (http://www.python.org/dev/peps/pep-3156/)
finally producing a working integration between Twisted and Gevent. Or
whatever Nick Coghlan wants to come up with, since he among anyone has the most
crossover knowledge of the async / ORM-related worlds I've seen.
O
I've been dealing with Twisted since the beggining of my ages with Python :)
What I can say: it's not an easy job. Here's what I see working:
1. Use Twisted Perspective Brokers to do the database job for you,
AFAIK is the most used combination of Twisted + SQA;
2. Use other types of message b
On Jun 12, 2013, at 2:47 PM, writes_on wrote:
> I'm building a Twisted application in Python 2.7 and am trying to use
> SqlAlchemy to interact with the database. I've got a working application that
> is leaking memory, and am not sure how to find the leaks. As a "maybe this is
> the problem"
I'm building a Twisted application in Python 2.7 and am trying to use
SqlAlchemy to interact with the database. I've got a working application
that is leaking memory, and am not sure how to find the leaks. As a "maybe
this is the problem" I'm asking if how I'm using SqlAlchemy might be the
sour
