Does anyone run more than one resque worker in a Heroku Dyno?
Given that unicorn usually manages more than one Rails server process, and
given that a Resque job runner probably consumes less resources than a Web
request, it should be possible to run more than one resque worker on a
single Heroku dyno.
Is anyone doing this successfully so far? My thoughts are, that an easy
way to do so would have the Procfile runs foreman, which then runs 2 (or
more) instances of the actual worker (i.e. rake resque:work)
Or is rake resque:workers up to that task? Resque itself does not
recommend using that method, as this starts workers in parallel threads
instead of in parallel processes.
Obviously, this makes sense only on i/o bound jobs.
No comments:
Post a Comment