-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
rustdoc: Optimize IdMap #96260
rustdoc: Optimize IdMap #96260
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 34e2d3b with merge 9342e57819dbf87e987f6c94aef9dd170cd69646... |
☀️ Try build successful - checks-actions |
Queued 9342e57819dbf87e987f6c94aef9dd170cd69646 with parent 51ea9bb, future comparison URL. |
Finished benchmarking commit (9342e57819dbf87e987f6c94aef9dd170cd69646): comparison url. Summary:
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. @bors rollup=never Footnotes |
For comparison, when this was applied after the PR which stops resolver cloning, it improved helloworld doc by almost 5 %. |
Nice. |
📌 Commit 34e2d3b has been approved by |
⌛ Testing commit 34e2d3b with merge 5915368c701f5cf205894c7d1b0e7aa0a480d60a... |
💔 Test failed - checks-actions |
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (de1bc00): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Slightly optimizes
IdMap
, which is hot inmarkdown_links
(context here). There are more improvements that can be made near this place, but this seemed like an easy win locally (although I tried it on top of #94857, so let's see what happens without that PR).r? @petrochenkov