5 ms·
Anyone have some insight on how this would compare performance-wise with Celery + RabbitMQ?
by freyrs3 16y ago
Anyone have some insight on how this would compare performance-wise with Celery + RabbitMQ?
- samratjp 16y agoThough I don't have direct experience with this particular one, I can tell you it's similarly implemented to Resque (the ruby async library). In my experience, Resque has been wicked fast thanks to Redis' excellent in-memory database. From my personal use cases, Redis has been pretty fast on both python and ruby. It really depends on what you are trying to do really. If you don't want additional moving parts and have Redis installed, I suppose this will do the job fine.
- praxxis 16y agoThe development version of Celery also supports Redis as a queue: http://ask.github.com/celery/tutorials/otherqueues.html http://ask.github.com/celery/tutorials/otherqueues.html
- simonw 16y agoI'm using Celery with the Redis backend for http://lanyrd.com/ http://lanyrd.com/
- frankwiles 16y agoWe're also using that with several clients.
- piotrSikora 16y agoIt doesn't really compare. HotQueue is just a queue. Celery is full-blown task queue (with periodic tasks, task retries, monitoring, etc) that supports multiple backends (AMPQ, Redis, SQL databases) and even integrates nicely with existing python web frameworks (Django, Flask).