oxidecomputer / oxidecomputer/crucible
Numbers for space usage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Thank you @rmustacc and @davepacheco for the great feedback.
@jmpesp / @leftwo , would you be willing to take a look at some of the comments directed towards Crucible? In particular, the idea that "if we are going to set a quota for Crucible dataset and avoid scaling it later, we should know up-front what the worst-case space usage is".
I'm not sure if we reached a number here, but it would be very helpful to have a ballpark - we have to set the quota as something concrete when we implement this.
Yes, @jmpesp and I will come up with some numbers.
Originally posted by @leftwo in https://github.com/oxidecomputer/rfd/issues/495#issuecomment-1245679734
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
No files, tests, or entry points are mentioned. Start by locating Crucible's dataset quota or space-accounting implementation, then establish and document a concrete worst-case space-usage estimate that can guide the quota value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100