3 ms·
Background workers only cost you money (5¢/hour) when they're running. It's prorated to the second. You can avoid running one constantly by using pedro's "autos
by wuputah 16y ago
Background workers only cost you money (5¢/hour) when they're running. It's prorated to the second. You can avoid running one constantly by using pedro's "autoscaling" branch, meaning you can run a few hours of background processing--which should equate to hundreds or thousands of jobs--every month for a few nickels.
http://github.com/pedro/delayed_job/tree/autoscaling http://github.com/pedro/delayed_job/tree/autoscaling
Pedro is a Heroku employee, so this use is totally fine by them, although the branch is not officially supported software.
[I'm friends with a few guys there, but I don't work there.]
- aarongough 16y agoI was just coming to the thread to post the exact same thing. I'm using the auto-scaling version of delayed_job in production on two applications and it has worked absolutely flawlessly. As the jobs are only for sending emails in the background I don't think I've racked up more that $1 over the last month...