Steps to optimize the Adobe Commerce Performance

1. www.vihadigitalcommerce.com

2. About VDC Over 8+ years & 1800+ projects, VDC is a full service ECommerce Web Development & Online Marketing Agency that provides value added services at affordable rates to numerous small, medium & large size of businesses across the world. Deliver 24×7 uptime and responsive digital commerce solutions that allow businesses to offer remote access of their professional offerings VDC is an offshore web development & online marketing center with agile approach of development www.vihadigitalcommerce.com

3. Steps to optimize the Adobe Commerce Performance ➔ When users experience a slow or unresponsive site, it affects conversion. ➔ We recommend following these steps to optimize the Adobe Commerce speed on cloud infrastructure implementation: ○ Assess the problem ○ Measure performance ○ Identify the part of the system critical for performance improvement ○ Modify part of the system to remove the bottleneck ○ Measure the performance after modification ○ If better, adopt it or revert www.vihadigitalcommerce.com

4. Recommendations to Improve Adobe Commerce Performance: 1) AEM with Adobe Commerce infrastructure Geographical location ➔ When developing pages, the initial provisioning of the two different infrastructures should be hosted within the same AWS (or Azure) Region to reduce latency between the AEM publisher and Adobe Commerce GraphQL 2) Adobe Commerce GraphQL caching ➔ Certain calls made by the user’s browser or AEM publisher to Adobe Commerce’s GraphQL will be cached in Fastly. ➔ Cache queries are often those that contain non-personal data and are unlikely to change frequently. For example, categories, categoryList, and products ➔ Those that are explicitly not cached are those that change often and, if cached, could endanger personal data and site functionality, such as cart and customerPaymentTokens inquiries ➔ Developers should keep this in mind while merging numerous queries to avoid accidentally bypassing potentially cacheable queries www.vihadigitalcommerce.com

5. 3) Catalog Flat Table ➔ It is not recommended to utilize flat tables for items and categories. Because using this outdated feature can cause performance degradations and indexing concerns, the flat catalog should be disabled via the Adobe Commerce admin, in the storefront area. ➔ Some third-party modules and customizations do require flat tables to function properly; it is advised that an evaluation be performed to understand the implications and dangers of having to use flat tables when opting to employ these extensions or customizations. 4) Fastly origin shielding ➔ Fastly origin shielding is disabled by default. The goal of Fastly’s origin shielding is to reduce traffic to the Adobe Commerce origin: when a request is received, a Fastly edge location (or “point of presence” / POP) scans for and provides cached material ➔ Fastly origin shielding can be activated in the Fastly configuration backend settings of your Adobe Commerce admin account. For optimal performance, select a shield location that is close to your Adobe Commerce origin data center www.vihadigitalcommerce.com

6. 5) Fastly image optimization ➔ When you enable Fastly origin shielding, you may also activate Fastly Image Optimizer. Where product catalog images are stored on Adobe Commerce, this service allows you to offload all resource-intensive product catalog image transformation processing onto Fastly and away from the Adobe Commerce origin. ➔ Fastly Image optimization can be enabled by selecting “enable deep image optimization” in Fastly setup in admin, but only after your origin shield has been active. Fastly image optimization will definitely help you in Adobe Commerce SEO optimization 6) Unused modules should be disabled ➔ Many modules become redundant and are not used when running Adobe Commerce headless, only delivering queries through the GraphQL endpoint, and no front-end shop pages are delivered directly from Adobe Commerce. ➔ By eliminating unnecessary modules, your Adobe Commerce code base becomes smaller and less complex, perhaps improving performance. Adobe Commerce modules can be disabled using composer www.vihadigitalcommerce.com

7. 7) Activation of MySQL and Redis connections ➔ MySQL and Redis Slave connections are not enabled by default in Adobe Commerce on the cloud. This is due to the fact that these settings are only appropriate for customers that anticipate a heavy load. ➔ To enable/disable slave connections for MySQL and Redis you should edit your .magento.env.yaml file to include the following: ◆ stage: ◆ deploy: ◆ MYSQL_USE_SLAVE_CONNECTION: true ◆ REDIS_USE_SLAVE_CONNECTION: true 8) Moving to a cloud-scaled (split) architecture for Adobe Commerce ➔ If, after all of the preceding setups, load test results or real infrastructure performance analysis show that the load levels to Adobe Commerce are constantly maxing out CPU and other system resources, then a shift to a scaled (split) architecture should be explored www.vihadigitalcommerce.com

8. Final Words: ➔ Hope this post will help you in Adobe Commerce Performance Optimization. If you still need any help, you can reach us at info@vihadigitalcommerce.com www.vihadigitalcommerce.com

9. Read the complete story follow the link below:- Steps to optimize the Adobe Commerce Performance Read Blog: https://www.vihadigitalcommerce.com/blog/ www.vihadigitalcommerce.com

10. LET'S GET TOGETHER Start Discussion About Your eCommerce Development & Online Marketing Hassle-free One Stop Solutions, Hire Us! Website: www.vihadigitalcommerce.com Skype: bdo3.magentoguys Email: info@vihadigitalcommerce.com Call: +91 7096620202