diff options
| author | Rémy Rakic <remy.rakic+github@gmail.com> | 2021-10-21 18:00:27 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-22 01:00:27 +0900 |
| commit | effa9e2a61e6f5712e6056afee9e19a6b30e69d7 (patch) | |
| tree | ea3a9e9ce38a5026af3f06c3fb564c9e56e88ecd /src/doc/rustc-dev-guide | |
| parent | 3bd8a0ed5298f5e8aca0004e5e6a8dcab4f286a5 (diff) | |
| download | rust-effa9e2a61e6f5712e6056afee9e19a6b30e69d7.tar.gz rust-effa9e2a61e6f5712e6056afee9e19a6b30e69d7.zip | |
Describe how to trigger perf runs (#1237)
Diffstat (limited to 'src/doc/rustc-dev-guide')
| -rw-r--r-- | src/doc/rustc-dev-guide/src/profiling.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/doc/rustc-dev-guide/src/profiling.md b/src/doc/rustc-dev-guide/src/profiling.md index ca0fee6d571..4851e3ee9d3 100644 --- a/src/doc/rustc-dev-guide/src/profiling.md +++ b/src/doc/rustc-dev-guide/src/profiling.md @@ -5,7 +5,10 @@ This section talks about how to profile the compiler and find out where it spend Depending on what you're trying to measure, there are several different approaches: - If you want to see if a PR improves or regresses compiler performance: - - The [rustc-perf](https://github.com/rust-lang/rustc-perf) project makes this easy and can be triggered to run on a PR via the `@rustc-perf` bot. + - The [rustc-perf](https://github.com/rust-lang/rustc-perf) project makes this easy and can be triggered to run on a PR via the `@rust-timer` bot. + The `@bors try @rust-timer queue` command, in a comment on the PR, will queue a try build and a + benchmarking run. + Note: you need `try` privileges to be able to do this. More details are available in the [perf collector documentation](https://github.com/rust-lang/rustc-perf/blob/master/collector/README.md). - If you want a medium-to-high level overview of where `rustc` is spending its time: - The `-Z self-profile` flag and [measureme](https://github.com/rust-lang/measureme) tools offer a query-based approach to profiling. |