Best practices and stability
This section provides technical recommendations for preparing Adobe Commerce environments—both Commerce on cloud infrastructure and on-premises—for high-traffic events such as the holiday season.
Upgrade to latest version of Adobe Commerce upgrade-to-latest-version-of-adobe-commerce
Ensure your site is not on an unsupported version of Adobe Commerce, which may affect your site’s performance and increase vulnerability to security issues. Upgrade to the latest version of Adobe Commerce to be secure and ready for the holiday season.
The latest release of Adobe Commerce includes many critical security fixes, including enhancements and mitigated issues, that will benefit your project when upgrading from a prior version.
For more information on unsupported versions of Adobe Commerce, review the Adobe Commerce Life Cycle Policy.
Install latest ECE-Tools and Quality Patch Tool (QPT) install-latest-ece-tools-and-quality-patch-tool-qpt
Ensure that the latest ece-tools module and its dependent modules are installed, using the --with-dependencies switch, so that all required cloud patches are properly installed for your Adobe Commerce version. For steps, see Update the ECE-Tools package.
Review the patch list available in the Quality Patches Tool and ensure the performance patches compatible with your Adobe Commerce version have been applied. See Quality Patches Tool: Search for patches.
Review and clean log files review-and-clean-log-files
Review the log files in the cloud environment (for example, application log files under ~/var/log) and identify any frequently logged records being written to the default or custom log files. For details, see View and manage logs.
- Review the following default log files and fix recurring errors:
~/var/log,~/var/log/exception.log,~/var/log/support_report.log,~/var/log/system.log,~/var/report. - Remove debug logs that were previously added for troubleshooting past issues.
These logs are also available in New Relic, see New Relic log management.
Monitor disk size growth monitor-disk-size-growth
Your Adobe Commerce on cloud infrastructure has two main disk volumes. Monitor these volumes to ensure they have sufficient free space when there is heavy traffic. Adobe Commerce provides a warning when either volume reaches above 70% usage.
/mnt/shared(shared files, including logs and media files)/data/mysql(database volume)
For details, see Manage disk space.
Review slowest database requests review-slowest-database-requests
It is important to regularly monitor and review the most time-consuming database transactions in New Relic. Investigate significantly slow queries and components.
-
Check the most time-consuming transactions: Go to New Relic > APM & Services > select environment > Databases, then sort by Most time consuming transactions.
-
Check the MySQL slow query log: Review
mysql-slow.logfor slow queries recorded by the system. These logs are also available in New Relic: go to New Relic > Logs, and filter byfilePath:"/var/log/mysql/mysql-slow.log".
Review the MySQL slow query logs regularly to confirm slow queries aren’t running frequently. For steps to resolve queries you identify as problematic, see Resolve database performance issues.
Configure cron jobs configure-cron-jobs
All asynchronous operations in Commerce are performed using the Linux cron command.
Commerce depends on proper cron job configuration for important system functions, including indexing and queue consumer operations. Failure to set it up properly means Commerce will not function as expected.
It is critical that Commerce cron is set up and configured correctly, using the appropriate Unix user in the Unix crontab file. Each Unix user has its own crontab file, which is the configuration used to run cron jobs for that user. For steps, see Configure and run cron jobs.
The script dev/tools/cron.sh can no longer be executed, because it has been removed.
Optimize client-side settings optimize-client-side-settings
To improve the storefront responsiveness of your Commerce instance, configure the following settings under Stores > Configuration > Advanced > Developer, which is available only in Developer mode:
- Grid Settings > Asynchronous indexing: Enable
- CSS Settings — Minify CSS Files: Yes
- JavaScript Settings — Minify JavaScript Files: Yes
- JavaScript Settings — Enable JavaScript Bundling: Yes (not enabled by default)
- Template Settings — Minify HTML: Yes
Since Adobe Commerce on Cloud always runs in Production mode, set each option from the command line instead—for example, bin/magento config:set --lock-config dev/css/minify_files 1—then commit the resulting app/etc/config.php change and redeploy. For the full list of CLI paths, see Optimize resource files.