-
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
rustc_metadata: Split children
into multiple tables
#110333
Conversation
(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 fac58797e3f5bbf6130e9467f4b23797a7837d4d with merge 17771203d49e1766373acad1b44f2afc0b25375e... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (17771203d49e1766373acad1b44f2afc0b25375e): 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)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. |
https://perf.rust-lang.org/compare.html?start=276fa294809e914b1d04192392d256814aa5ce1a&end=17771203d49e1766373acad1b44f2afc0b25375e&stat=size%3Acrate_metadata Metadata size has regressed somewhat (expectedly). I wonder why binary size has also increased 🤔. |
children
into multiple tableschildren
into multiple tables
Ok, that's not very good. |
This comment has been minimized.
This comment has been minimized.
What. |
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 unless you want to do a force-push or something to verify that error is unrelated to the PR.
@bors r=compiler-errors rollup=maybe |
📌 Commit c7174a73d698b20849e605838a1f4db74a656475 has been approved by It is now in the queue for this repository. |
⌛ Testing commit c7174a73d698b20849e605838a1f4db74a656475 with merge 58e1e837cc5f356fadedaa7ea48b6e29d5dbeca9... |
This comment has been minimized.
This comment has been minimized.
This comment was marked as resolved.
This comment was marked as resolved.
instead of merging everything into a single bag. If it's acceptable from performance point of view, then it's more clear to keep this stuff organized more in accordance with its use.
@bors r=compiler-errors |
Rollup of 5 pull requests Successful merges: - rust-lang#110333 (rustc_metadata: Split `children` into multiple tables) - rust-lang#110501 (rustdoc: fix ICE from rustc_resolve and librustdoc parse divergence) - rust-lang#110608 (Specialize some `io::Read` and `io::Write` methods for `VecDeque<u8>` and `&[u8]`) - rust-lang#110632 (Panic instead of truncating if the incremental on-disk cache is too big) - rust-lang#110633 (More `mem::take` in `library`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
instead of merging everything into a single bag.
If it's acceptable from performance point of view, then it's more clear to keep this stuff organized more in accordance with its use.