Low commit activity in last 3 years
A long-lived project that still receives updates
When your resque jobs are frequent and fast, the overhead of forking and running your after_fork might get too big.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

Runtime

>= 0
>= 1.27.0, < 2.7
 Project Readme

resque-multi-job-forks

Installation

Add this line to your application's Gemfile:

gem 'resque-multi-job-forks'

And then execute:

$ bundle

Or install it yourself as:

$ gem install resque-multi-job-forks

Version compatibility

  • For resque 1.27 and later, use 0.5.0 or later.
  • For resque 1.26, use 0.4.5.

(this should be handled correctly by bundler, but mentioning just in case)

Usage

If you have very frequent and fast resque jobs, the overhead of forking and running your after_fork hook might get too big. Using this resque plugin, you can have your workers perform more than one job before terminating.

By default, each forked process will work for 1 minute. Specify a different amount of time using the MINUTES_PER_FORK environment variable:

QUEUE=* MINUTES_PER_FORK=5 rake resque:work

Or, specify the number of jobs you want each fork to process using the JOBS_PER_FORK environment variable:

QUEUE=* JOBS_PER_FORK=1000 rake resque:work

This will have each fork process 1000 jobs, before terminating. If both environment variables are set, MINUTES_PER_FORK will be ignored.

If you have a job that relies on each Resque job running in its own process, you can disable this plugin for that job:

QUEUE=* DISABLE_MULTI_JOBS_PER_FORK=true rake resque:work

This plugin also defines a new hook, that gets called right before the fork terminates:

Resque.before_child_exit do |worker|
  worker.log("#{worker.jobs_processed} were processed in this fork")
end

Note on Patches/Pull Requests

  • Fork the project.
  • Make your feature addition or bug fix.
  • Add tests for it. This is important so I don't break it in a future version unintentionally.
  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
  • Send me a pull request. Bonus points for topic branches.

Copyright

Copyright (c) 2010 Mick Staugaard. See LICENSE for details.