rust-lang / rust-lang/rustc-perf
Consider running new benchmarks on old artifacts
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 732
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
When we add new benchmarks, we typically don't run them on old artifacts, but we could (at least to a certain point in history). While this might not bring a ton of insight when adding regression focused benchmarks (e.g., stress tests), it would likely be very useful when adding new "real world" crates.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by tracing how new benchmarks are run against existing artifacts and how artifact history is selected. Clarify the historical cutoff and which benchmark categories should be included, then verify that runs against old artifacts produce comparable results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100