-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
perf check: inline valtree constructors #99166
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 0889c9d with merge fd25cb153abc1779e4f4b6ab14250aa607919e5a... |
☀️ Try build successful - checks-actions |
Queued fd25cb153abc1779e4f4b6ab14250aa607919e5a with parent 38b7215, future comparison URL. |
Finished benchmarking commit (fd25cb153abc1779e4f4b6ab14250aa607919e5a): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
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 may lead to changes in compiler perf. @bors rollup=never Footnotes |
Nope, what wasn't it. 🤷 @rust-lang/wg-compiler-performance are the Max RSS benchmarks very noisy? I don't see how this change can have those RSS impacts. |
Yes, they are quite noisy indeed. Usually if only 1-2 benchmarks are changed, that's noise. Real changes usually materialize as a large number of changes across the board. |
Let's see if this helps with the perf regression from #98957.
r? @oli-obk