We can give a try for Sidekiq – Ruby background job processor.(it’s faster than resque in terms of processing)
http://mperham.github.com/sidekiq/
https://github.com/mperham/sidekiq
https://github.com/mperham/sidekiq/wiki/Testimonials

Some of point about Sidekiq

  • Sidekiq enables background processing via threads. it uses a pool of threads to process jobs so at most you have one master process.
  • Sidekiq is Resque compatible so we can use with existing Resque code and then process them using new Sidekiq workers.
  • Internally Sidekiq uses the Celluloid actor library to make threading easier and safer to manage.

 

Resque:

Pros:

  • does not require thread safety (works with pretty much any gem out there);
  • has no interpreter preference (you can use any ruby);
  • loads of plugins.

Cons

  • runs a process per worker (uses more memory);
  • does not retry jobs (out of the box, anyway).

Sidekiq:

Pros

  • runs thread per worker (uses much less memory);
  • less forking (works faster);
  • more options out of the box.

Cons

  • [huge] requires thread-safety of your code and all the dependencies. If you run thread-unsafe code with threads, you’re asking for trouble;
  • much less plugins (at the moment there are only 2);
  • works on some rubies better than others (jruby and rubinius are recommended).

reference : http://stackoverflow.com/questions/11580954/resque-vs-sidekiq
https://github.com/mperham/sidekiq/wiki/FAQ

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s