https://github.com/andrew/sidekiq

Simple, efficient background processing for Ruby

https://github.com/andrew/sidekiq

Science Score: 10.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
    3 of 332 committers (0.9%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (14.8%) to scientific vocabulary

Keywords from Contributors

authorization oauth2 oauth2-client oidc oidc-client data-engineering
Last synced: 9 months ago · JSON representation

Repository

Simple, efficient background processing for Ruby

Basic Info
  • Host: GitHub
  • Owner: andrew
  • License: other
  • Language: Ruby
  • Default Branch: master
  • Homepage: http://sidekiq.org
  • Size: 15.6 MB
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 2
  • Open Issues: 0
  • Releases: 0
Fork of sidekiq/sidekiq
Created over 10 years ago · Last pushed over 10 years ago
Metadata Files
Readme Changelog Contributing License

README.md

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

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

Owner

  • Name: Andrew Nesbitt
  • Login: andrew
  • Kind: user
  • Location: Bristol, UK
  • Company: @ecosyste-ms and @octobox

Working on mapping the world of open source software @ecosyste-ms and empowering developers with @octobox

GitHub Events

Total
Last Year

Committers

Last synced: 9 months ago

All Time
  • Total Commits: 2,065
  • Total Committers: 332
  • Avg Commits per committer: 6.22
  • Development Distribution Score (DDS): 0.453
Past Year
  • Commits: 0
  • Committers: 0
  • Avg Commits per committer: 0.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
Mike Perham m****m@g****m 1,130
Brandon Hilkert b****t@g****m 87
Jonathan Hyman j****n@p****u 46
jc00ke j****e@j****m 44
Abdelkader Boudih t****e@g****m 38
Ryan LeCompte l****e@g****m 26
Anton Davydov a****o@g****m 21
Justin Mazzi j****i@g****m 16
Max Spransy m****s@g****m 15
Aaron Ackerman t****7@g****m 11
Brian Goff c****3@g****m 11
Jason Coene j****e@g****m 11
Thorsten Ball m****t@g****m 8
Ismael Abreu i****a@g****m 7
Jake Mack j****k@g****m 7
Peter M. Goldstein p****n@g****m 7
Philip Hallstrom p****p@p****m 7
Tyson Tate t****n@t****m 7
perldork p****k@w****m 7
grosser m****l@g****t 6
Andrea Singh i****o@m****m 6
awaw a****w@n****w 6
Romain Dardour r****n@u****r 6
Rob Chekaluk r****b@h****) 6
Niels Kristian n****s@a****m 6
Moser, Kevin K****r@n****m 6
Manish Valechha m****h@l****m 6
Jack Royal-Gordon j****g@p****m 6
Ezekiel Templin z****e@t****n 5
Daisuke Taniwaki d****i@g****m 5
and 302 more...

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 0
  • Total pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Total issue authors: 0
  • Total pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
Top Labels
Issue Labels
Pull Request Labels