You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to improve Magento 2 capacity to absorb a big amount of charge, I think one of the most important improvement to do is to add a new dedicated cache for the Swatches. Whatever the website that uses M2 swatches, PLP, and PDP displays is dependant on the async load of the JSON of the swatches. The calculation of the JSON is causing a big part of the server charge and limit the capacity of M2 to scale up.
Expected behavior (*)
Add a new cache call "swatches caches", with by default a 1h lifetime to load PDP ad PLP really faster. This cache may be ideally served by Redis.
Benefits
Improve Magento 2 PLP, and PDP load time, and improve Magento 2 capacity to support a bigger charge.
Additional information
The text was updated successfully, but these errors were encountered:
Hi @gsa83. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results
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:
@magento give me 2.4-develop instance - upcoming 2.4.x release
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
📞 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
Description (*)
In order to improve Magento 2 capacity to absorb a big amount of charge, I think one of the most important improvement to do is to add a new dedicated cache for the Swatches. Whatever the website that uses M2 swatches, PLP, and PDP displays is dependant on the async load of the JSON of the swatches. The calculation of the JSON is causing a big part of the server charge and limit the capacity of M2 to scale up.
Expected behavior (*)
Add a new cache call "swatches caches", with by default a 1h lifetime to load PDP ad PLP really faster. This cache may be ideally served by Redis.
Benefits
Improve Magento 2 PLP, and PDP load time, and improve Magento 2 capacity to support a bigger charge.
Additional information
The text was updated successfully, but these errors were encountered: