RQ as backend? #28
-
I heavily rely on RQ and Django-task-scheduler (formerly django-rq-scheduler). Do you see the RQ worker itself implemented as a backend? It relies on forking to a new process for every task (preventing memory leaks). Also, what about simultaneous tasks? It would allow for further reducing costs. Thanks! |
Beta Was this translation helpful? Give feedback.
Answered by
RealOrangeOne
Jun 8, 2024
Replies: 1 comment
-
Yes, there could absolutely be an RQ-based backend. It wouldn't be something which would be integrated into Django itself, but it could happily live either within |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
RealOrangeOne
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, there could absolutely be an RQ-based backend. It wouldn't be something which would be integrated into Django itself, but it could happily live either within
django-tasks
, or in its own separate package.