I'm also using redis for both brokering and caching. So far, so good. My use case consists in one HUGE (5 hours) task, and several tiny (30s or less) scheduled tasks.
Cheers, AT On Mon, Nov 28, 2011 at 10:54 AM, Carlos Daniel Ruvalcaba Valenzuela < clsdan...@gmail.com> wrote: > Celery has a bunch of alternative brokers, depending on your > constrains you may not need something as "heavy" as RabbitMQ, you > could for example use db broker if you don't have many tasks, it is > slower but does not add a new server (apart from celery) to your > stack, other option is to use Redis as a broker, redis is light and > very fast, you can limit the amount of memory used by it too. > > Check the celery page for alternative brokers. I have tested DB broker > and works ok, redis broker worked wonders in another setup where it > was also being used for caching. > > Regards, > Carlos Daniel Ruvalcaba Valenzuela > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
