oxidecomputer / oxidecomputer/crucible
Time to consider parallel dispatch
Open
Nobody has claimed this yet.
multiple-subvolumes
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
From this XXX comment
And also at
It's time to consider the parallel dispatch.
Not only for IO operations, but also downstairs activation.
At the moment, things are performed serially and that can't be good for performance.
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 reading upstairs/src/volume.rs at lines 562 and 774, along with the linked blame and source context. Determine how IO operations and downstairs activation are currently dispatched serially; done means defining and implementing a parallel-dispatch approach for both areas, with performance implications understood.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100