Slow category loading due to configurable product swatches

[ioweb-gr]

Preconditions and environment

• 2.4.7-p1

Steps to reproduce

Create a website with many configurable products (we have around 4m total products including variations) and each one should have at around 250 variations.
Finally load a category with 30 products while the cache is not fresh.

The page will take too long to load > 20s

Initially on Magento 2.4.6 we realized it was the swatches display which we disabled afterwards.

However when we upgraded the problem became apparent once again due to the swatches being loaded even if disabled in the backend.

Expected result

Page loads fast

Actual result

By profiling with blackfire we noticed that the system spends a lot of time in loading option prices

Resulting in 5 seconds of queries extra in the load apart from cpu processing.

By checking the renderer.phtml template we notice it's loading swatches configuration even if they're not enabled in the backend configuration option.

Additional information

There are two issues to solve here

1. Performance with swatches enabled
2. Disable loading the swatches in the category if the configuration option is not enabled in the backend

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ioweb-gr. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ 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, join the Community Contributions Triage session to discuss the appropriate ticket.

[ruospo]

Any news for this issue?

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hello @ioweb-gr,

Thanks for the report and collaboration!

We have tried to reproduce the issue in the latest 2.4-develop branch but the issue is not reproducible for us. We have followed the below steps to reproduce the issue:

1. Run the extra_large performance toolkit to create the products.
2. Reindex the products and clear the cache.
3. Try to navigate the category in the frontend where products > 30,000:
   
4. For us the page loads in 9.22 seconds.

Please let us know in case we missed anything.

Thanks