Have your resque workers process more that one job
Clone or download
Pull request Compare This branch is 16 commits ahead, 8 commits behind staugaard:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.



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. The original use case for this project was keeping connections while fetching data from a very fragile and crappy webservice.

You simply specify the number of jobs you want each fork to run using the JOBS_PER_FORK environment variable:

QUEUE=* JOBS_PER_FORK=5 rake resque:work

You have to specify JOBS_PER_FORK environment variable or else your jobs won't run with this gem

This will have each fork 5 jobs, before terminating.

This plugin also defines 2 new hooks that get called after the fork starts and before the fork terminates

Resque.before_perform_jobs_per_fork do |worker|
  worker.log("Your message here")

Resque.after_perform_jobs_per_fork do |worker|
  worker.log("Your message here")

Version 1.15.x works on Resque 1.15.x

Version 0.5.x works on Resque 1.11.x

Version 0.4.x works on Resque 1.10.x

Version 0.3.x works on Resque 1.8.x

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 © 2010-2012 Sam Granieri (Inspired by Mick Staugaard). See LICENSE for details.