Uh oh!
There was an error while loading. Please reload this page.
perf check: inline valtree constructors - #99166
Conversation
RalfJung
commented
Jul 11, 2022
@bors try @rust-timer queue |
rust-timer
commented
Jul 11, 2022
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Jul 11, 2022
⌛ Trying commit 0889c9d with merge fd25cb153abc1779e4f4b6ab14250aa607919e5a... |
bors
commented
Jul 11, 2022
☀️ Try build successful - checks-actions |
rust-timer
commented
Jul 11, 2022
Queued fd25cb153abc1779e4f4b6ab14250aa607919e5a with parent 38b7215, future comparison URL. |
rust-timer
commented
Jul 12, 2022
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 |
RalfJung
commented
Jul 12, 2022
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. |
Kobzol
commented
Jul 12, 2022
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