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
2015-08-24 10:38:19 -07:00
bin Use Process.kill instead of kill 2015-08-06 11:07:43 +02:00
examples rsn 2015-07-29 15:37:24 -07:00
lib backwards compat, #2505 2015-08-24 10:38:19 -07:00
myapp merge master 2015-08-15 14:02:37 -07:00
test Fix thread warning in test_web 2015-08-16 13:38:13 -07:00
web Have enqueued_at time be nil for jobs that have yet to be enqueued (i.e., are scheduled). 2015-08-16 11:15:53 -04:00
.gitignore Add worker generator test 2014-10-21 22:55:40 +08:00
.travis.yml See how jruby-head (2.2 compatible) does on sidekiq 2015-02-25 11:47:56 +01:00
3.0-Upgrade.md Use new proc syntax instead all Proc.new 2015-06-10 23:10:16 +03:00
Changes.md Update change log to fix "typo" 2015-08-21 10:31:02 -06:00
COMM-LICENSE New commercial license v201508 2015-08-03 09:55:44 -07:00
Contributing.md update notes, prepare for release 2015-02-05 12:24:52 -08:00
Ent-Changes.md enterprise 0.7.1 release 2015-08-17 15:22:17 -07:00
Gemfile Verify test suite running with Rails 3.2 2015-07-13 22:00:22 -07:00
LICENSE Move copyright to contribsys 2014-07-17 13:53:54 -07:00
Pro-2.0-Upgrade.md Note that Redis Sentinel should be safe to use 2015-07-02 11:15:20 -07:00
Pro-Changes.md pro changes 2015-08-07 12:00:17 -07:00
Rakefile allow every test to be run with just ruby test/xxx_test.rb 2014-12-30 12:54:58 -08:00
README.md wordsmithing 2015-08-17 15:31:11 -07:00
sidekiq.gemspec merge master 2015-08-15 14:02:37 -07:00

Sidekiq

Gem Version Code Climate Build Status Gitter Chat

Simple, efficient background processing for Ruby.

Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background 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 jobs 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 10 200MB resque processes to peg your CPU whereas one 300MB Sidekiq process will peg the same CPU and perform the same amount of work.

Requirements

I test with the latest MRI (2.2, 2.1 and 2.0) and JRuby versions (1.7). Other versions/VMs are untested but might work fine. MRI 1.9 is no longer supported.

All Rails releases starting from 3.2 are officially supported.

Redis 2.4 or greater is required.

Installation

gem install sidekiq

Getting Started

See the sidekiq home page for the simple 3-step process. You can watch Railscast #366 to see Sidekiq in action. If you do everything right, you should see this:

Web UI

Want to Upgrade?

I also sell Sidekiq Pro and Sidekiq Enterprise, extensions to Sidekiq which provide more features, a commercial-friendly license and allow you to support high quality open source development all at the same time. Please see the Sidekiq homepage for more detail.

More Information

Please see the sidekiq wiki for the official documentation. mperham/sidekiq on Gitter is dedicated to this project, but bug reports or feature requests suggestions should still go through issues on Github. Release announcements are made to the @sidekiq Twitter account.

You may also find useful a Google Group dedicated to Sidekiq discussion and a Sidekiq tag on Stack Overflow.

Problems?

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, chat in Gitter, 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.

Thanks

Sidekiq stays fast by using the JProfiler java profiler to find and fix performance problems on JRuby. Unfortunately MRI does not have good profile tooling.

License

Please see LICENSE for licensing details.

Author

Mike Perham, @mperham / @sidekiq, http://www.mikeperham.com / http://www.contribsys.com