47ca099093
task wasn't dropping pid file, use current_path everywhere. |
||
---|---|---|
bin | ||
examples | ||
lib | ||
myapp | ||
test | ||
web | ||
.gitignore | ||
.rvmrc | ||
Changes.md | ||
COMM-LICENSE | ||
config.ru | ||
Gemfile | ||
LICENSE | ||
Rakefile | ||
README.md | ||
sidekiq.gemspec | ||
TODO.md |
Sidekiq
Simple, efficient message processing for Ruby.
Sidekiq aims to be 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.
Sidekiq is different from Resque in how it processes messages: it processes many messages concurrently per process. Resque only processes one message at a time per process so it is far less memory efficient. 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.5 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.
License
Please see LICENSE for licensing details.
Author
Mike Perham, @mperham, http://mikeperham.com