rustc-perf
rustc-perf copied to clipboard
Website for graphing performance of rustc
> It'd be good to add these flags to rustc-perf's incr tests once this flag is implemented, I think, FWIW. _Originally posted by @Mark-Simulacrum in https://github.com/rust-lang/rust/issues/85864#issuecomment-851587323_ For examples in the...
We should list fixed benchmarks, not just newly broken ones.
While doing triage this week for: https://perf.rust-lang.org/perf/triage?start=e2116acae59654bfab2a9729a024f3e2fd6d4b02 I found that the title for every PR is listed as "" in the report. For example: ``` #### Regressions [#91224](https://github.com/rust-lang/rust/issues/91224) - Moderate...
Looking at the performance report [linked here](https://github.com/rust-lang/rust/pull/89611#issuecomment-975033770): Benchmark & Profile | Scenario | % Change | Significance Factor ? -- | -- | -- | -- encoding opt | full...
This comparison was categorized as probably relevant - https://perf.rust-lang.org/compare.html?start=7611fe438dae91084d17022e705bf64374d5ba4b&end=bcfd3f7e88084850f87b8e34b4dcb9fceb872d00&stat=instructions:u - but I think it is definitely so, due to the wide range of -doc benchmarks affected.
The triage report has improved, but its focus is largely on highlighting single changes impacts on the performance of the Rust compiler. We should think more holistically about what we...
Following up on https://github.com/rust-lang/rust/pull/88832, it seems like a reasonable step may be to restrict bors merges to only happen after any existing perf regressions have been justified. This might have...
Right now, these only include -opt/-debug/-check builds.
Please consider asking perf to record the total number of syscalls for a build, and offering that as a comparison metric. That can be really useful when doing library-level optimizations...
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...