rust-lang / rust-lang/rustc-perf
Show automatically detected regressions and improvement
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 732
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
Although the data can be noisy I've found it pretty obvious when there's a regression or an improvement. Basically any persisted regression for 3+ builds (or improvement) is typically here to stay. Would be awesome if there were a "trophy case" for improvements and a way to easily scan for regressions. Ideally we could tag regressions with upstream rust-lang/rust issues, but that's probably a bit too fancy!
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
Start by mapping how rustc-perf stores and displays results across builds; the issue names no files, tests, or entry points. Define how persisted regressions and improvements should be detected and presented, then determine how users would scan regressions and whether upstream issue links belong in scope.
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