oxidecomputer / oxidecomputer/crucible
Collect propolis tuning into one place
Open
Nobody has claimed this yet.
mvp
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Document tuning options for crucible in one place if possible.
Some things that must be determined:
Amount of IO we will hold before forcing a flush
Amount of IO we will hold when a downstairs goes away before we give up.
Queue depth for unanswered IO requests (but still connected)
I'll add more when I think of them.
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 searching the Crucible repository for the tuning options named in the issue: flush behavior, downstairs failure timeouts, and unanswered IO queue depth. Done means the identified options and their purpose are documented together in one place, with room for additional tuning settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100