celery

This algorithm assumes that a user is a person, so some of its matches are incorrect: - atom - caskroom - mongoid - celery - etc.

Gevent and celery I have found don't play well together even if you disable Gevent for the worker.

We did this for a Flask app that used celery, redis, etc and we were happy with it.

My life got better when I stopped using Celery and instead started using Redis or RabbitMQ directly.

Lay down a layer of celery in the bottom of the Slow Cooker.

Is that with Celery or are you using your own queue management?

I think you could use this with celery tasks so as long as each worker used a different PID file.

In my experience Celery brings more cost in complexity than value.

I don't know how much of it is truth but I've definitely had problems with Celery and memory leaks in the past myself.

At my last job we used Docker extensively for developing our main software product, based on a Django + PostgreSQL + RabbitMQ + Celery stack.

We recently built out a small background task runner - we were told to use RQ+Redis rather than Celery because (and I'm repeating hearsay here) - 1.

I've found a few problems with celery myself.

The solutions for running cron-like tasks on Python are not very mature, everybody seems to be using Celery.

Interesting to hear they were so dissatisfied with Celery/RabbitMQ that chose to write their own queuing system.

I'm looking in to implementing a queue for background tasks right now, and was down to choosing between Celery/RabbitMQ and beanstalkd.