@bors try @rust-timer queue

Awaiting bors try build completion.

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

⌛ Trying commit 4fed4eaf1f47808054a466a0ebfbc1ab43d05062 with merge aa96faefcac093683ce6ac76663721b8e8add3ce...

☀️ Try build successful - checks-actions
Build commit: aa96faefcac093683ce6ac76663721b8e8add3ce (aa96faefcac093683ce6ac76663721b8e8add3ce)

Queued aa96faefcac093683ce6ac76663721b8e8add3ce with parent 427eba2, future comparison URL.

Finished benchmarking commit (aa96faefcac093683ce6ac76663721b8e8add3ce): comparison url.

Summary: This benchmark run shows 204 relevant regressions 😿 to instruction counts.

• Average relevant regression: 1.4%
• Largest regression in instruction counts: 6.9% on incr-unchanged builds of match-stress-enum check

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.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

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

@bors try @rust-timer queue

Awaiting bors try build completion.

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

⌛ Trying commit 8e079de with merge c7c009da733590badf6d357d014b264d2116a76f...

☀️ Try build successful - checks-actions
Build commit: c7c009da733590badf6d357d014b264d2116a76f (c7c009da733590badf6d357d014b264d2116a76f)

Queued c7c009da733590badf6d357d014b264d2116a76f with parent 24b8bb1, future comparison URL.

Finished benchmarking commit (c7c009da733590badf6d357d014b264d2116a76f): comparison url.

Summary: This benchmark run shows 47 relevant regressions 😿 to instruction counts.

• Average relevant regression: 0.5%
• Largest regression in instruction counts: 1.0% on incr-unchanged builds of match-stress-enum check

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.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

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

OK, the hash map is clearly visible in perf... before we do anything fancy, can you try just using a vec map or even a btreemap?

@bors try @rust-timer queue

Awaiting bors try build completion.

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

⌛ Trying commit 6c0fdf0ed39afdef9af32d3a0f4c296f6a6f8064 with merge 329ad690a748dafcb9b572adf1e1a5aaa902a576...

@bors try @rust-timer queue

Awaiting bors try build completion.

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

⌛ Trying commit cbfa7ce with merge b79b1d9741593752d8ab835d5e0d7af5c767c677...

☀️ Try build successful - checks-actions
Build commit: b79b1d9741593752d8ab835d5e0d7af5c767c677 (b79b1d9741593752d8ab835d5e0d7af5c767c677)

Queued b79b1d9741593752d8ab835d5e0d7af5c767c677 with parent a924ef7, future comparison URL.

Finished benchmarking commit (b79b1d9741593752d8ab835d5e0d7af5c767c677): comparison url.

Summary: This benchmark run shows 11 relevant regressions 😿 to instruction counts.

• Average relevant regression: 0.7%
• Largest regression in instruction counts: 1.3% on full builds of deep-vector opt

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.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

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

@bors r+ rollup=never

📌 Commit d82a7bc has been approved by oli-obk

⌛ Testing commit d82a7bc with merge 8ebec97...

☀️ Test successful - checks-actions
Approved by: oli-obk
Pushing 8ebec97 to master...

Finished benchmarking commit (8ebec97): comparison url.

Summary: This benchmark run did not return any relevant results. 54 results were found to be statistically significant but too small to be relevant.

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

@rustbot label: -perf-regression