oxidecomputer / oxidecomputer/propolis
propolis should limit tokio workers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
By default, the tokio runtime will spawn a number of worker threads equal to the number of visible logical CPUs it finds on the system. No instance should ever be able to make use of all that CPU (especially since it has its own separate threads for driving the guest vCPUs), so it would make sense to limit the number of threads created by the tokio runtime.
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 by locating where propolis initializes the Tokio runtime and review how guest vCPU threads are created. Determine an appropriate worker limit that prevents one instance from using all visible CPUs without interfering with vCPU work. Done means the runtime applies that limit and relevant behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100