procrastinate VS rq

I did find this PR which adds a much more detailed description of what to do, although some of it is a bit outdated.

What about https://github.com/procrastinate-org/procrastinate (postgresql task queue with transactions & stuff)

If you're using PostgreSQL, then

django-postgres-queue: https://github.com/gavinwahl/django-postgres-queue

procrastinate: https://github.com/procrastinate-org/procrastinate/

We chose the Procrastinate library to run periodic tasks.

That's pretty cool. Reckon it would work with existing code that calls Redis over the wire for RQ?

  https://python-rq.org

https://github.com/rq/rq is to the rescue.

We use RQ[0], it has Redis as a dependency. It’s pretty straightforward and we’re very happy with it. If you are using Django you may want to look at Django RQ[1] as well. RQ has built in scheduling capabilities these days, but historically it did not so we used (and still use) RQ Scheduler[2] which I think still has some advantages over the built in stuff.

[0] https://python-rq.org/

Also had a similar experience using RabbitMQ with Django+Celery. Extremely complicated and workers/queues would just stop for no reason.

Moved to Python-RQ [1] + Redis and been rock solid for years now.

[1] https://python-rq.org/

Yep, rq is simple and good: https://python-rq.org/ It also has a Django wrapper: https://github.com/rq/django-rq

We have a GPU (G5) instance that uses Python RQ (https://python-rq.org/).