-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Some perf experiments #101561
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
Some perf experiments #101561
Conversation
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
@bors try @rust-timer queue include=libc,bitmaps,many-assoc-items |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 2c9cd17 with merge 10d870608eaa08538f193fe3a636577d0660000b... |
☀️ Try build successful - checks-actions |
the perf bot has probably lost this one ?! |
@rust-timer build 10d870608eaa08538f193fe3a636577d0660000b |
Queued 10d870608eaa08538f193fe3a636577d0660000b with parent 4af35b8, future comparison URL. |
Finished benchmarking commit (10d870608eaa08538f193fe3a636577d0660000b): comparison URL. Overall result: no relevant changes - no action neededBenchmarking 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 Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. |
That was fast ?! |
"No results" on the comparison page. |
I expanded the view, they are all too small to be shown. But if you select "Show non-relevant results" you'll get more data |
Oh I thought nothing ran 😅 |
These 3 benchmarks are pretty quick to run and the queue was empty :) |
#101561 (comment) included only a couple of benchmarks, though we should probably surface that on result completion too. |
r? @ghost
looking at regression from #99102 (comment)