New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[do not merge] Hashbrown performance after Hashbrown PR #277 #87193
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 35105f781ec4d07e86ec4700bd83262992109078 with merge 9e0bddae0e3963ad4e1059a2fbc67b8f924065f2... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
35105f7
to
082c914
Compare
@bors try @rust-timer queue |
⌛ Trying commit 082c914c026a163527859322146c6e2424c94ad3 with merge cbce48a16e4e575ed3fd942ad01f1f6731fd8fa0... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit f7d16ffd7c6ab1a9188fe085cb9937986688eebd with merge 532fc783a82edd5e8503640b96eeb4ad58dec438... |
☀️ Try build successful - checks-actions |
Queued 532fc783a82edd5e8503640b96eeb4ad58dec438 with parent c49895d, future comparison URL. |
Finished benchmarking try commit (532fc783a82edd5e8503640b96eeb4ad58dec438): comparison url. Summary: This change led to significant mixed results 🤷 in compiler performance.
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 perf run, please indicate this with @bors rollup=never |
⌛ Trying commit 6b180eda54d37979a7ea1fe7665df6de426570ab with merge e3d53a8dda3f4013ee67323592b615c981b50816... |
☀️ Try build successful - checks-actions |
Queued e3d53a8dda3f4013ee67323592b615c981b50816 with parent e742158, future comparison URL. |
Finished benchmarking try commit (e3d53a8dda3f4013ee67323592b615c981b50816): comparison url. Summary: This change led to significant mixed results 🤷 in compiler performance.
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 perf run, please indicate this with @bors rollup=never |
6b180ed
to
c6d30cd
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit c6d30cd with merge 6ebaa581fcddde8735fcb573a63a73429b7ebfe7... |
☀️ Try build successful - checks-actions |
Queued 6ebaa581fcddde8735fcb573a63a73429b7ebfe7 with parent 9cf1944, future comparison URL. |
Finished benchmarking try commit (6ebaa581fcddde8735fcb573a63a73429b7ebfe7): comparison url. Summary: This change led to significant mixed results 🤷 in compiler performance.
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 perf run, please indicate this with @bors rollup=never |
r? @Amanieu