kotovalexarian-likes-github/mperham--sidekiq
1
0
Fork 0
mirror of https://github.com/mperham/sidekiq.git synced 2022-11-09 13:52:34 -05:00
Code Releases Activity
Simple, efficient background processing for Ruby
1341 commits 15 branches 164 tags 17 MiB
Ruby 82%
HTML 14.3%
JavaScript 2.8%
CSS 0.9%
Find a file
Mike Perham 093ca901ee Merge pull request #1081 from feedbin/workers_size 
User workers_size instead of workers.size for better performance.
2013-07-28 09:27:12 -07:00
bin Remove superfluous binary and remove examples from gem 2013-03-03 16:24:36 -08:00
examples Bugfix of "status" returning false for version "2.12.1". 2013-06-07 13:16:26 -03:00
lib Memoize workers_size. 2013-07-28 09:17:33 -07:00
myapp Benchmark setup, 56s for 1.9.3, 50s for 2.0.0 2013-06-30 12:15:19 -07:00
test Merge pull request #1062 from LeakyBucket/master 2013-07-17 09:50:00 -07:00
web User workers_size instead of workers.size for better performance. 2013-07-28 08:52:07 -07:00
.gitignore Allow setting of a custom timeout for the Redis Connection Pool 2013-07-16 15:40:50 -06:00
.travis.yml Revert travis config. 2013-02-01 12:26:03 -05:00
Changes.md Make Chain enumerable 2013-07-27 16:14:07 -07:00
COMM-LICENSE Add commercial license for Sidekiq Pro 2012-10-04 09:34:56 -07:00
config.ru Add delete and retry now operations to web UI 2012-03-29 20:55:16 -07:00
Contributing.md Add contribution guide, version bump 2013-07-21 15:36:01 -07:00
Gemfile Relax slim version constraint, fixes #970 2013-06-01 14:15:14 -07:00
LICENSE Add commercial license for Sidekiq Pro 2012-10-04 09:34:56 -07:00
Pro-Changes.md Latest Pro changes! 2013-07-27 16:16:25 -07:00
Rakefile Test cleanup 2012-03-17 21:36:33 -07:00
README.md Prefer background jobs to message processing in future terminology 2013-06-25 21:55:51 -07:00
sidekiq.gemspec Prefer background jobs to message processing in future terminology 2013-06-25 21:55:51 -07:00

README.md

Sidekiq

Gem Version Code Climate Build Status Coverage Status

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 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 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.

Requirements

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.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, 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.

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.

There's also a mailing list via Librelist that you can subscribe to by sending an email to sidekiq@librelist.org with a greeting in the body. To unsubscribe, send an email to sidekiq-unsubscribe@librelist.org and that's it! Once archiving begins, you'll be able to visit the archives to see past threads.

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 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.

License

Please see LICENSE for licensing details.

Author

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