On Mon, Jan 16, 2012 at 3:05 PM, bryan hunt <[email protected]> wrote: > Gearman only supports a MySql backend for persistent queues - it > doesn't support a real message queue like Rabbitmq. > > > > On Jan 16, 10:33 am, Cherian Thomas <[email protected]> wrote: >> Second Arun’s suggestion on gearman. Pretty solid too.
Gearman also would require a separate process for each project that you have operating in it. If you think about it, that is a bit of a non-requirement, since every distributed task queue will require a daemon process to attach to it to receive work, and if they are different projects, they will clearly require separate processes. With celery/rabbitmq, you can run as many django projects, with as many celeryd instances per project, as you want. You don't need a 1:1 mapping between projects and celeryd instances, we run many celeryd instances for a single project (across many boxes). Each project should use a separate vhost on rabbitmq, which you configure with settings.BROKER_VHOST. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en.
