-
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
Add a per-item query just for define_opaque
attributes
#138500
Conversation
rustbot has assigned @petrochenkov. Use |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
…, r=<try> Add a per-item query just for `define_opaque` attributes follow up to rust-lang#128440 (comment) This wasn't done in the previous PR to make sure we can gauge the perf effect independently of the other changes
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (6bf40d9): comparison URL. Overall result: ❌ regressions - please read the text belowBenchmarking 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary 1.1%, secondary 3.1%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 775.364s -> 773.892s (-0.19%) |
cc @lcnr ^ moving it into the OwnerInfo is not feasible at present |
follow up to #128440 (comment)
This wasn't done in the previous PR to make sure we can gauge the perf effect independently of the other changes