bin | ||
examples | ||
lib | ||
myapp | ||
test | ||
web | ||
.gitignore | ||
.rvmrc | ||
Changes.md | ||
COMM-LICENSE | ||
config.ru | ||
Gemfile | ||
LICENSE | ||
Rakefile | ||
README.md | ||
sidekiq.gemspec |
Sidekiq
Simple, efficient message processing for Ruby.
Sidekiq uses threads to handle many messages at the same time in the same process. It integrates tightly with Rails 3 to make background message processing dead simple.
Sidekiq is compatible with Resque. It uses the exact same message format as Resque so it can integrate into an existing Resque processing farm. You can have Sidekiq and Resque run side-by-side at the same time and use the Resque client to enqueue messages in Redis to be processed by Sidekiq.
At the same time, Sidekiq uses multithreading so it is much more memory efficient than Resque (which forks a new process for every job). You'll find that you might need 50 200MB resque processes to peg your CPU whereas one 300MB Sidekiq process will peg the same CPU and perform the same amount of work. Please see my blog post on Resque's memory efficiency and how I was able to shrink a Carbon Five client's resque processing farm from 9 machines to 1 machine.
Requirements
I test on Ruby 1.9.3 and JRuby 1.6.x in 1.9 mode. Other versions/VMs are untested but I will do my best to support them. Ruby 1.8 is not supported.
Installation
gem install sidekiq
Getting Started
See the sidekiq home page for the simple 4-step process.
More Information
Please see the sidekiq wiki for more information. #sidekiq on irc.freenode.net is dedicated to this project, but bug reports or feature requests suggestions should still go through issues on Github.
There's also a mailing list via Librelist that you can subscribe to by sending and email to sidekiq@librelist.org with a greeting in the body. To unsubscribe, send an email to sidekiq-unsubscribe@librelist.org and that's it! Once archiving begins, you'll be able to visit the archives to see past threads.
License
Please see LICENSE for licensing details.
Author
Mike Perham, @mperham, http://mikeperham.com