Simple, efficient message processing for Ruby.
Sidekiq uses threads to handle many messages at the same time in the same process. It does not require Rails but will integrate 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.
I test on Ruby 1.9.3 and JRuby 1.7.x. Other versions/VMs are untested but I will do my best to support them. Ruby 1.8 is not supported.
Redis 2.0 or greater is required.
gem install sidekiq
Want to Upgrade?
I also sell Sidekiq Pro, an extension to Sidekiq which provides more features, a commercial-friendly license and allows you to support high quality open source development all at the same time. Please see the Sidekiq Pro homepage for more detail.
There's also a mailing list via Librelist that you can subscribe to by sending an email to email@example.com with a greeting in the body. To unsubscribe, send an email to firstname.lastname@example.org and that's it! Once archiving begins, you'll be able to visit the archives to see past threads.
Please do not directly email any Sidekiq committers with questions or problems. A community is best served when discussions are held in public.
If you have a problem, please review the FAQ and Troubleshooting wiki pages. Searching the issues for your problem is also a good idea. If that doesn't help, feel free to email the Sidekiq mailing list or open a new issue. The mailing list is the preferred place to ask questions on usage. If you are encountering what you think is a bug, please open an issue.
Please see LICENSE for licensing details.