oxidecomputer / oxidecomputer/crucible
Volume: improve performance when there is a read-only parent
Open
Nobody has claimed this yet.
mvp
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Performing multiple reads (to the read only parent and affected sub volume) adds latency. We should figure out how to improve the performance in the presence of a read only parent.
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
The issue does not name any files, tests, or entry points. Begin by locating the volume read path and the handling of read-only parents, then establish a benchmark for reads involving both the parent and affected subvolume; done means reduced latency with coverage for the optimized behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100