There are no hard limits; it's just that it wasn't designed for long- running tasks so you may not find it suitable. For example if you've set up a task to run every 10 minutes, but the task doesn't finish before the next scheduled run hits, you could end up with an escalating problem.
On Cedar apps, Scheduler jobs will run in their own Dyno, but on Bamboo, they'll hijack an existing web dyno so you may see impact on web traffic. Memory cap is the same as for any other dyno. On Nov 23, 7:22 pm, Thariq S <[email protected]> wrote: > Hello, > > I was glad to hear about the Heroku scheduler in the monthly Heroku > newsletter, but I have some questions. In the FAQ it somewhat > ominously says: "Scheduled jobs are meant to execute short running > tasks or enqueue longer running tasks into a background job queue such > as Delayed Job. Anything that takes longer than a couple of minutes to > complete should use a worker process to run." > > Why is it that it's meant specifically for short running jobs? Is it > that the scheduler uses one of your dyno's instead of spinning off > another process, meaning that when it's running your dyno will serve > web pages slower? Is this enforced, is there a timeout somewhere? What > about a memory cap? > > Thanks, > > Thariq -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
