You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 26, 2022. It is now read-only.
Celery + beat continue to bite me in the butt whenever I stop looking at them, I don't think this "queue worker + queue scheduler pushing tasks at a steady rate" is healthy. Maybe it is time to change.
There are a couple of other queue systems in python but as far as I remember, they don't try to solve this particular problem.
Maybe a queue system is not the correct paradigm, as there are very few heavy jobs that are actually initiated by the user and need queueing:
A couple things that happen on log in
Twitter archives (haha rip)
Everything else just needs to happen on a schedule.
The text was updated successfully, but these errors were encountered:
Celery + beat continue to bite me in the butt whenever I stop looking at them, I don't think this "queue worker + queue scheduler pushing tasks at a steady rate" is healthy. Maybe it is time to change.
There are a couple of other queue systems in python but as far as I remember, they don't try to solve this particular problem.
Maybe a queue system is not the correct paradigm, as there are very few heavy jobs that are actually initiated by the user and need queueing:
Everything else just needs to happen on a schedule.
The text was updated successfully, but these errors were encountered: