1
0
Fork 0
mirror of https://github.com/mperham/sidekiq.git synced 2022-11-09 13:52:34 -05:00
Simple, efficient background processing for Ruby
Find a file
Mike Perham 6af6a86369 Refactor middleware API, this will break anyone using the old API.
e.g.
Sidekiq::Processor.middleware => Sidekiq.server_middleware
Sidekiq::Client.middleware => Sidekiq.client_middleware
2012-02-18 12:12:05 -08:00
bin Cleanup 2012-02-12 20:48:13 -08:00
examples Adding Sinatra example 2012-02-12 22:34:37 -08:00
lib Refactor middleware API, this will break anyone using the old API. 2012-02-18 12:12:05 -08:00
myapp Add support for new delay extensions for ActiveRecord and ActionMailer, with example tests in myapp. 2012-02-17 21:24:14 -08:00
test Refactor middleware API, this will break anyone using the old API. 2012-02-18 12:12:05 -08:00
.gitignore Ignore rbx dir 2012-02-12 20:59:27 -08:00
.rvmrc jruby fix 2012-02-12 21:16:49 -08:00
Changes.md Housekeeping 2012-02-17 22:04:18 -08:00
COMM-LICENSE Add GPL and commercial license info 2012-01-24 19:44:57 -08:00
Gemfile Integrate simplecov 2012-01-23 21:02:54 -08:00
LICENSE Update sidekiq licensing to avoid GPL incompatibilities 2012-02-07 08:51:39 -08:00
Rakefile SimpleCov fixes 2012-01-23 22:07:21 -08:00
README.md Update sidekiq licensing to avoid GPL incompatibilities 2012-02-07 08:51:39 -08:00
sidekiq.gemspec Move redis connection logic into class. Add support for namespaces via redis-namespace gem 2012-02-09 10:26:43 -06:00
TODO.md Refactor middleware API, this will break anyone using the old API. 2012-02-18 12:12:05 -08:00

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.

License

Please see LICENSE for licensing details.

Click here to lend your support to Open Source and make a donation at www.pledgie.com !

Author

Mike Perham, @mperham, http://mikeperham.com