oxidecomputer / oxidecomputer/omicron
Cosmo Mupdate takes more time than Gimlet
Open
Nobody has claimed this yet.
cosmo
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
The total time to update via wicket was double for a cosmo sled from a gimlet sled. Some of this might be expected but we should at least understand the difference.
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 with the wicket update path and compare the timing of Cosmo and Gimlet sled updates. Measure the two workflows and trace where their durations diverge. Done means the difference is explained and any actionable cause is documented or addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100