rust-lang / rust-lang/rustc-perf
Record max-rss on the rustc build benchmark
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 733
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
Max-rss is even more important than wall time when building rustc on low end devices. A high wall time would just take a while to build, while a high max-rss would completely prevent builds if the address space is exhausted or would merely cause it to grind to a halt when ram is exhausted and swap has to be used.
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 locating the rustc build benchmark and reading how it currently records wall time. Add max-rss recording alongside the existing benchmark result, then verify that the benchmark exposes max-rss so builds on low-end devices can be compared by memory use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100