Closed MarioVilas closed 10 years ago
This could be of use too, we should check it out: http://gearman.org/download/
What about ActiveMQ, I use ActiveMQ currently. http://activemq.apache.org/
Good idea, I've added it to the ticket description.
@cr0hn proposes using kombu, and I think he's right. It's a pure-Python module that wraps over other messaging libraries when available and falls back to a pure-Python implementation of an AMQP client when missing, so it pretty much gives us the best of both worlds.
In fact, with any luck we could just use Celery directly to replace both the messaging system and the process pool. https://github.com/celery/celery
Yes, celery can be the better option and, if we want (in the future), also can be integrated with django:
http://ask.github.io/celery/tutorials/clickcounter.html
El 10/12/2013, a las 18:31, Mario Vilas notifications@github.com escribió:
In fact, with any luck we could just use Celery directly to replace both the messaging system and the process pool. https://github.com/celery/celery
— Reply to this email directly or view it on GitHub.
Closing as duplicate of #228.
Right now we're using Python's multiprocessing module for everything, but the way it uses pipes has proven to be somewhat inefficient. I think we would benefit from using a proper message queue.
Main options are:
However we need a pure-Python fallback to keep the core platform independent. A pure-Python MQ implementation would be ideal for this.