Suggestion: resque-scheduler support?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 456
- Forks
- 149
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 3
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how resque-pool launches and manages workers, then compare that lifecycle with resque-scheduler’s process model. Define the expected configuration and verify that the scheduler can run alongside the worker pool without a separate full-memory worker; the issue provides no file or test to target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100