Avoid starting threads in umbrella process
Open
Nobody has claimed this yet.
core/quality
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 616
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Currently, the umbrella process starts quite a number of threads where it's questionable if they are actually needed or just wasting resources. Check if we can get rid of them. Maybe this even allows us to simplify other code as fork() is way easier in a single-threaded process.
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
No files, tests, or entry points are named. Trace how the umbrella process starts its threads, identify which are required, and check the effects of removing them on fork() and related process setup. Done means the unnecessary threads are removed without breaking process startup or resource handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100