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
Complex products children ids are not cached in Type class leading to multiple unnecessary db requests #30585
Comments
Moving this feature request to magento2 issues as this looks to be a performance bug that should be addressed |
Hi @PierreLeMaguer. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
For more details, please, review the Magento Contributor Assistant documentation. Please, add a comment to assign the issue:
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues 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 |
✅ Confirmed by @sivaschenko Issue Available: @sivaschenko, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself. |
Description
in the product page, the method 'getChildrenIds' is called several times and each time we make an SQL request to get this info.
For example juno-jacket.html with the sample data, the method of the configurable type is called 20 times.
The problem
The result of this method is not stored in a cache to avoid to make useless request.
benefits
We earn time by making a cache and storing the results instead of making SQL requests.
Related pull request closed due to inactivity: #23910
The text was updated successfully, but these errors were encountered: