-
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
perf: Only search potentially changed constraints in lexical_region_resolve #68001
Conversation
r? @davidtwco (rust_highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion |
perf: Only search potentially changed constraints in lexical_region_resolve Gives a big performance increase to the unicode_normalization benchmark in my testing.
☀️ Try build successful - checks-azure |
Queued fe4e15c with parent f48e576, future comparison URL. |
Finished benchmarking try commit fe4e15c, comparison URL. |
@bors r+ |
📌 Commit d9f3888 has been approved by |
@bors rollup=never |
☔ The latest upstream changes (presumably #68034) made this pull request unmergeable. Please resolve the merge conflicts. |
Should reduce the number of elements as well as branches in the extremely hot loop and process_constraint in benchmarks such as unicode_normalization
d9f3888
to
917eb18
Compare
Rebased to fix conflicts |
@bors r+ |
📌 Commit 917eb18 has been approved by |
perf: Only search potentially changed constraints in lexical_region_resolve Gives a big performance increase to the unicode_normalization benchmark in my testing.
☀️ Test successful - checks-azure |
Gives a big performance increase to the unicode_normalization benchmark in my testing.