-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should we replace Celery with Heroku scheduler? #326
Comments
I think I'd vote for using the heroku scheduler. Right now the advantages seem to weigh over. |
Since the tasks themselves would still be in code, i don't mind too much that the schedule is defined outside the repo, and makes it easier to move to a different scheduler in the future if we want. We could also choose to document the scheduling in the repo in a |
@bfirsh @jessykate, I looked up the heroku scheduler. It's very coarse; every 10 minutes, every hour, daily. That's it. Perhaps it'd be better to use this method instead -> https://devcenter.heroku.com/articles/clock-processes-python Though that still requires one worker... so it's not saving any money (or perhaps it's saving some? Right now it looks like there is one worker for celeryd). But it would reduce any complexity as it would be more like a normal cronjob. |
We actually have pretty light weight scheduling needs. I haven't looked at the various options but the heroku scheduler seems like it would save us a good $25 or $50/mo 😮 ! I'm kind of keen on that since MN doesn't make very much and i'd rather spend it on humans doing dev work if we have the option?? :) |
Yeah we don't need fine grained scheduing. The only thing that is run is sending out emails in the morning, and a weekly one too (which can be done with The clock process they describe is effectively what Celery is. |
Celery is only used to run scheduled tasks (sending emails, etc) and is not used to run any background tasks.
Now we are moving to Heroku, we could use the Heroku Scheduler to run these tasks instead of Celery.
Advantages:
Disadvantages:
The text was updated successfully, but these errors were encountered: