No commit activity in last 3 years
No release in over 3 years
When your resque jobs are frequent and fast, the overhead of forking and running your after_fork might get too big. You may limit by either job limit or time limit per fork.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 0.3.0

Runtime

>= 1.9.10
 Project Readme

resque-multi-job-forks¶ ↑

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.

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

QUEUE=* MINUTES_PER_FORK=5 rake resque:work

This will have each fork process jobs for 5 minutes, before terminating.

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 © 2010 Mick Staugaard. See LICENSE for details.