[DO NOT MERGE] Perf test for rustdoc

[aDotInTheVoid]

Judging the impact of a change

@rustbot modify label: -S-waiting-on-review +S-experimental

@bors try @rust-timer queue

[rust-highfive]

r? @CraftSpider

(rust-highfive has picked a reviewer for you, use r? to override)

[aDotInTheVoid]

@bors try @rust-timer queue

[rust-timer]

Insufficient permissions to issue commands to rust-timer.

[bors]

@aDotInTheVoid: 🔑 Insufficient privileges: not in try users

[jyn514]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 386e5cd with merge e6f2702984d826acc540a997499e7a1c12d86c42...

[jyn514]

@rust-timer build=e6f2702984d826acc540a997499e7a1c12d86c42

[jyn514]

@rust-timer build e6f2702984d826acc540a997499e7a1c12d86c42

[rust-timer]

Queued e6f2702984d826acc540a997499e7a1c12d86c42 with parent 454cc5f, future comparison URL.

[rust-timer]

Finished benchmarking commit (e6f2702984d826acc540a997499e7a1c12d86c42): comparison url.

Summary: This benchmark run did not return any relevant changes.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf -perf-regression