Skip to content
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

Add a Swatches cache #33229

Open
gsa83 opened this issue Jun 14, 2021 · 1 comment
Open

Add a Swatches cache #33229

gsa83 opened this issue Jun 14, 2021 · 1 comment

Comments

@gsa83
Copy link

gsa83 commented Jun 14, 2021

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

@m2-assistant
Copy link

m2-assistant bot commented Jun 14, 2021

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

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this


⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Feature Requests Backlog
  
Ready for Grooming
Development

No branches or pull requests

1 participant