-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Use SmallVec
in bitsets
#109458
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
Use SmallVec
in bitsets
#109458
Conversation
This doesn't increase their size and means that we don't have to heap allocate for small sets.
r? @wesleywiser (rustbot has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 29c1132 with merge 0c8d05b63a32307e32af27b76105d7a892f90ec0... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me if perf is ok
Finished benchmarking commit (0c8d05b63a32307e32af27b76105d7a892f90ec0): comparison URL. Overall result: ❌✅ regressions and improvements - 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis 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. |
Maybe const eval uses a bitsest and the access to it got slower because of the smallvec? I'll try looking deeper later (as const eval perf is quite important imo due to Miri) |
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
⌛ Testing commit 29c1132 with merge 6196dc5223c3904b29f935948258804aafabb726... |
💔 Test failed - checks-actions |
@bors retry |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Test successful - checks-actions |
Finished benchmarking commit (2d429f3): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis 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.
CyclesResultsThis 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.
|
Improvements outweigh the regressions and for some of the regressions, it should be fine to ignore the result as noise. @rustbot label: +perf-regression-triaged |
This doesn't increase their size and means that we don't have to heap allocate for small sets.