a6ea55d16f
On OpenBSD, you can only use getpgid(pid) if the calling process belongs to the same session as the the process with the PID `pid'. Otherwise getpgid() returns EPERM. Using kill(0, pid) is a more portable way to check whether a process exists. |
||
|---|---|---|
| bin | ||
| examples | ||
| lib | ||
| myapp | ||
| test | ||
| web | ||
| .gitignore | ||
| .travis.yml | ||
| 3.0-Upgrade.md | ||
| 4.0-Upgrade.md | ||
| Changes.md | ||
| COMM-LICENSE | ||
| Contributing.md | ||
| Ent-Changes.md | ||
| Gemfile | ||
| LICENSE | ||
| Pro-2.0-Upgrade.md | ||
| Pro-3.0-Upgrade.md | ||
| Pro-Changes.md | ||
| Rakefile | ||
| README.md | ||
| sidekiq.gemspec | ||
Sidekiq
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.8 or greater is required.
Installation
gem install sidekiq
Getting Started
See the Getting Started wiki page and follow the simple setup process. You can watch Railscast #366 to see Sidekiq in action. If you do everything right, you should see this:
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 Reddit area 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. StackOverflow or Reddit 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 multithreaded profiling tools.
License
Please see LICENSE for licensing details.
Author
Mike Perham, @mperham / @sidekiq, http://www.mikeperham.com / http://www.contribsys.com