-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Remove EntryKind from metadata. #98960
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit aa7c0b72385fda97913f98749ecba4d05b3e6465 with merge a4011cb6eef91e3830bdf2f739c3b5140ce6720a... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit aa7c0b72385fda97913f98749ecba4d05b3e6465 with merge d39a35a69b824686f9f79ec1e99fa347a28d685f... |
☀️ Try build successful - checks-actions |
Queued d39a35a69b824686f9f79ec1e99fa347a28d685f with parent 41ad4d9, future comparison URL. |
Finished benchmarking commit (d39a35a69b824686f9f79ec1e99fa347a28d685f): comparison url. Instruction count
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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit adb0576b6c900e8dc7f2272bc0ff50afdde590b9 with merge 46ef832c457b61f5d20f548ba382df88edb88f58... |
Last perf run suggests that both the crate metadata and the dep graph got bigger. |
☀️ Try build successful - checks-actions |
Queued 46ef832c457b61f5d20f548ba382df88edb88f58 with parent 5b8cf49, future comparison URL. |
Finished benchmarking commit (46ef832c457b61f5d20f548ba382df88edb88f58): comparison url. Instruction count
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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
☔ The latest upstream changes (presumably #101152) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors r+ rollup=never |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2e35f95): comparison URL. Overall result: ❌ regressions - no action needed@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.
CyclesThis benchmark run did not return any relevant results for this metric. Footnotes |
This PR continues the refactor of metadata emission to be more systematic, iterating on definitions and filtering based on each definition's
DefKind
. This allows to remove the largeEntryKind
enum, replaced by linear tables in metadata.