If you don't mind using Resque instead of Delayed:Job for your workers, take a look at this blog post.
http://blog.darkhax.com/2010/07/30/auto-scale-your-resque-workers-on-heroku That should be just about all you need to spin up your workers up and down as needed. On Aug 31, 10:50 pm, Gabriel <ummo...@gmail.com> wrote: > This seems to be a somewhat common use case for Heroku: I have a > process that takes far too long to tie up a web request but doesn't > happen often enough to warrant paying for a Worker. > > Right now I'm considering calling fork to handle this situation and I > have two questions: > > 1. Will this work on Heroku? That is: are there any specifics about > the Heroku architecture that would prevent forks? > > 2. Is there a better way that doesn't involve having a Worker running > all the time? I've seen people mention that Workers can be spun up > and deleted programmatically but I've yet to see what the API for > doing so looks like. > > Thanks, > > Gabriel -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
