vello_cpu: Bring your own thread-pool
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4.3k
- Forks
- 300
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 61
Description
Currently `vello_cpu::RenderContext::new_with` only offers an option to control the number of threads of the thread-pool. That thread-pool is per RenderContext, so with multiple contexts you get multiple threadpools. It would be nice if we could bring our own thread-pool, so we can re-use the same pool and don't need to spawn more threads for each RenderContext.
Upstream servo issue: https://github.com/servo/servo/issues/46992
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
Start with vello_cpu::RenderContext::new_with and trace how its per-context thread-pool is created and stored. Review the upstream Servo issue for expected API behavior. Done means callers can provide one pool for multiple RenderContext values without each context spawning its own threads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100