Explore: Adjust the number of workers based on generation
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 834
- Forks
- 36
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 7
Description
This remain to be seen whether we'll actually need this, but would be worth exploring.
The assumption is that the first few generation will invalidate shared pages rather quickly, as such the peak memory usage at first might get quite high.
A possible solution to this would be to start with a lower number of workers to compensate for the lower CoW effectiveness, and then increase the number of workers of processes with each new generation.
This would mean pitchfork needs a bit of a warm up before achieving peak throughput.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating how worker counts and generations are managed, then establish whether generation-based worker scaling improves memory usage without sacrificing throughput; done requires a measured, agreed approach and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100