Aaron Van Bokhoven

I am a Hawaii based Software Developer and a Film Photographer.
  • I guess you could call me a "full stack developer".
  • I love coding with Ruby and Ruby on Rails, and I love shooting with film.
  • I have a love/hate relationship with Ember.js, and Backbone.js.
  • I currently live in Honolulu, Hawaii, but frequent Chicago and California.
  • I believe that programming is a form of art, like painting and photography, where you can express your ideas and logic and see it transform into something real.
Aaron Van Bokhoven
Email me at bokhoven@gmail.com. View my Photo Blog. I'm also on Twitter.

October 27, 2010
You're viewing an article, go back to the home page to see more.

Do you need a delayed_job job to happen at certain times or intervals?

This one is easy and I use it quite often - particularly to scrape data at certain times during the day, and generate nightly statistics and reports.

Why would I use delayed_job to handle recurring jobs over rake task?
Every time a rake task is issued, a new rails instance is spawned which takes time and memory to start and run. If a delayed_job daemon is already running, using that will save both. In my opinion, running a rake task that uses the rails environment is usually very costly in production and should be avoided if possible.

© Aaron Van Bokhoven