Open
Description
This might be out of left field and way out of scope.
Could this gem support running an instance of resque-scheduler alongside various workers?
Asking because resque-scheduler takes up nearly as much memory as a standard worker but never does "real" work. So a fork for it as part of the pool might significantly reduce its memory footprint.
Maybe?