rustc-perf icon indicating copy to clipboard operation
rustc-perf copied to clipboard

Website for graphing performance of rustc

Results 140 rustc-perf issues
Sort by recently updated
recently updated
newest added

Hi! I tend to work on performance-sensitive parts of the compiler so I check performance locally a lot. In the current setup this requires me to run a docker script...

help wanted

Viewing graphs on perf.rust-lang.org often takes a long time, seemingly mainly spent waiting for a response from the server when loading data: ![image](https://github.com/rust-lang/rustc-perf/assets/1974256/535bc331-d111-4fc2-8ff7-1580e8e5c767) Are the current bottlenecks here already well...

Time displayed at https://perf.rust-lang.org/status.html for took/expected heavily differs for some runs, while perf result shows no difference. For example, for run https://github.com/rust-lang/rust/pull/115388#issuecomment-1701235905 Step | Took | Expected -- | --...

The JSON output format is taking more and more importance in rustdoc and we reached a point where performance checks would start to make sense. Now, with that said, this...

I am trying to run the "Local profile (diff)" command given on [this page](https://perf.rust-lang.org/detailed-query.html?commit=94b77248c5aa991f2597b4a1c1a49e297ac2f3e2&base_commit=3071e0aef6dfd0a150c3fb1da0abad4ec86ca0aa&benchmark=ctfe-stress-5-debug&scenario=full&sort_idx=-11). Unfortunately it doesn't work: ``` $ ./target/release/collector profile_local cachegrind +3071e0aef6dfd0a150c3fb1da0abad4ec86ca0aa --rustc2 +94b77248c5aa991f2597b4a1c1a49e297ac2f3e2 --include ctfe-stress-5 --profiles Debug...

is there any plans/scope for "extracting" the `size:` metrics out from under the "compile-time" header now that there's a grouping for artefact sizes? or am I entirely missing the point?

Didn't bisected where that started, but https://perf.rust-lang.org/status.html ``` Cannot compile match-stress Caused by: expected success, got exit status: 101 stderr= Documenting match-stress v0.1.0 (/tmp/.tmpUt7JXo) warning: unclosed HTML tag `baz` -->...

2023-05-23 triage used this url: https://perf.rust-lang.org/?start=3ea9ad532474343426e564b997891e459cda89a6&end=cda5becc27cbc7106646fbc40aacea5e7896d954&absolute=false&stat=instructions%3Au 2023-05-30 triage used this url: https://perf.rust-lang.org/?start=cda5becc27cbc7106646fbc40aacea5e7896d954&end=1221e43bdf413f7c405e9b17ef19d76c88222098&absolute=false&stat=instructions%3Au why did PR https://github.com/rust-lang/rust/pull/111807 show up in both triage runs? The end of the first is equal to...

C-bug

1. the 1-feature.patch makes cargo compile-able on OS without openssl pre-installed like osx; 2. RUSTC=rustc_fake makes the build script which depends on `Command::new("RUSTC")` failed like [autocfg](https://github.com/cuviper/autocfg/blob/e75324cfa5fa0bec4f06f9609ab169bb7747f984/src/lib.rs#L156)

I am in a team for compiler development. Not related to Rust, but developing under MLIR framework Finding a way to track the performance of our compiler (both compilation speed...