oxidecomputer / oxidecomputer/crucible
Add measure_iops to CI
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
From some other PR, measure_iops generated some perf numbers.
It shouldn't take that long that you have to ask! :) It should be on the order of minutes, like 2 or 3, for a 2G disk running locally.
Originally posted by @jmpesp in https://github.com/oxidecomputer/crucible/issues/650#issuecomment-1452378931
If it only takes a few minutes to run, we should throw it on the end of one of the other perf CI tests.
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 existing measure_iops implementation and the performance CI tests in the repository. Add measure_iops to the end of an appropriate performance CI test, then verify it completes locally on a 2G disk in roughly two or three minutes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100