oxidecomputer / oxidecomputer/crucible
Upstairs should record IO completion stats per downstairs
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
A useful metric could be how many times each downstairs was "the first" to respond to
an IO request. Maybe even recording first/second/third, depending on the difficulty of gathering that
information at IO completion time.
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 locating the upstairs IO completion path and the code that tracks downstairs responses. Determine whether first, second, and third responders can be identified when an IO completes; done means recording per-downstairs completion statistics in a defined, useful form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100