-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Generator matching optimization #31613
Generator matching optimization #31613
Conversation
Hi @kirmorozov. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. 🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
@magento run all tests |
@magento run Functional Tests B2B, Functional Tests CE |
Hi @kirmorozov, thanks for contributing! Can you provide some extra information on execution time improvement? Ideally, we need to see the difference between your solution and vanilla Magento. Can you provide that information? Thanks! |
Thanks for asking, difference is visible at scale. It all comes to
Here is some opcode to read.
Some benchmarks and ranks can be form with 3rdparty sources |
@magento run Functional Tests CE |
@gabrieldagama Do you think that switch to str_ends_with and polyfill is better? |
Hi @bgorski, thank you for the review.
|
Sorry, I answered too soon before properly analysing the screenshot. @kirmorozov: you'd probably best rebase your change on top of the latest OR @engcom-Hotel could temporarily downgrade his composer version to version 1.x ( |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
I merged the latest 2.4-develop to the PR branch myself to speed up the process a bit |
@magento run Functional Tests CE, Functional Tests EE, WebAPI Tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@engcom-Hotel I noticed you added the "Progress: needs update" tag here. May I know what changes are requested here? Were you able to re-test this? |
✔️ QA Passed Hello @kirmorozov, Thanks for the contribution! We have tested the PR. Please have a look into below description: Manual testing scenario:
Before: ✖️ After: ✔️ Tested all the manual scenarios, no impact on regression testing. Thanks |
Hi @kirmorozov, thank you for your contribution! |
Description (*)
Changed implementation to be more transparent, and easy to read.
Plus using one strlen with explicit variable, rather than 3 implicit (via php internals for each strlen and minus operation).
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)
Resolved issues: