CODEWITHSUNDEEP
ruby-on-railsruby-on-rails-3herokudelayed-job
donald
donald

Reputation: 23757

Rails 3 + Heroku + Delayed jobs - Help me understand!

I'm having problems understanding this article: http://blog.darkhax.com/2010/07/30/auto-scale-your-resque-workers-on-heroku .

I don't quite get it why do I need Redis + Resque when I have delayed jobs provided by Heroku.

From my understanding, I still have to pay for the workers, correct? What's my main advantage of using that solution?

Regards.

Upvotes: 2

Views: 1386

Answers (4)

user1966241
user1966241

Reputation:

You can also use Hirefireapp.com to monitor and scale your apps

Upvotes: 0

Hollownest
Hollownest

Reputation: 1067

hirefireapp is a new-ish simple drop-in solution to auto-scaling workers.

It spawns workers for you based on queue size (configurable) and then "fires" them when they are no longer necessary. You pay for the dyno time (to the nearest second) and for the hirefireapp service. In theory you could roll your own using the open source hirefire gem too.

It also handles scaling the web side if you choose, so you can spawn more web dynos based on current latency.

Upvotes: 0

Nader
Nader

Reputation: 5595

To autoscale heroku workers using delayed job, you can hook into the enqueue and after hooks and use the heroku api to query/update the number of workers.

For the most basic implementation on enqueue, check to see if there are workers and if not add a worker. On after, check to see if there are other delayed jobs and if not reduce the workers to 0.

You can obviously make this more sophisticated in the way that you scale.

Here is a basic implementation: https://github.com/phaza/Heroku-Delayed-Job-Autoscale

Upvotes: 0

Adam Lassek
Adam Lassek

Reputation: 35515

If you don't know why you need Resque, then you don't need it ;)

Resque is for high-scalability. delayed_job is fine for smaller-scale stuff, but once you get to the size of, say, Github, you will need something like Resque. If delayed_job works for you, then stay with it. You don't need to worry about replacing it until your background jobs queue gets around 30,000 or so.

Upvotes: 3

Related Questions