400+ stores and try to Save configuration taking too much time and CPU spike > 100%

[jigar48]

Preconditions and environment

• Magento 2.4.6

I have 400+ stores created in single Magento instance, I have autoscaling server with different Database AWS server.

There are 200k products.

Frontend and Backend both are hosted on AWS with autoscaling ability.

I have AWS elasticache Redis server configured in the env.php

Steps to reproduce

1. Open Admin panel
2. Go to Stores -> Configuration
3. Just click on Save config button
4. Check CPU usage on SSH
5. It Spike to > 100% and Frontend servers are down

Expected result

It should not spike CPU to 100%

Actual result

Additional information

I was trhoubleshooting this issue since month we think that it trying to clean Cache and Save cahce while saving configuration for 400 stores and that causing issue.

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] 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[bot]]

Hi @jigar48. 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.

[hostep]

Magento 2.4.7 comes with a solution for this I believe, see the new async config feature they introduced in version 2.4.7: https://experienceleague.adobe.com/en/docs/commerce-operations/performance-best-practices/configuration#asynchronous-configuration-save

(if you have a working cronjob, then there is no reason to manually run that bin/magento queue:consumers:start command they recommend, it should start up automatically via the cronjob, unless your configuration doesn't allow it)