oxidecomputer / oxidecomputer/crucible
Test performance impact of different pipeline lengths
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
When https://github.com/oxidecomputer/crucible/pull/449 lands, the Upstairs will be async, and support submitting multiple requests and await'ing on all of them at the same time. In crudd, test the performance impact of different pipeline lengths.
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
Review the issue's dependency on PR #449 and the existing crudd entry point. Once the Upstairs async changes are available, measure performance with several pipeline lengths and compare the results. Done means the performance impact of those lengths is recorded clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100