This article provides a patch for the known Magento Commerce Cloud 2.2.1 issue related to having low site and API performance caused by a long time required to write debug.log.
Issue
Site performance is slow. API operations run slowly, for example updating products using the PUT method. When you take a closer look at the operations using NewRelic, most memory and CPU is consumed by writing to /var/log/debug.log.
Solution
To solve the issue, apply the patch. The patch splits and writes the log, payment, and shipping methods logs to separate files.
Patch
The patch is attached to this article. To download it, scroll down to the end of the article and click the file name, or click the following link:
Download MDVA-8371_EE_2.2.1_COMPOSER_v2.patch
Compatible Magento versions
The patch was created for:
- Magento Commerce Cloud 2.2.1
The patch is also compatible (but might not solve the issue) with the following Magento versions and editions:
- Magento Commerce Cloud, Magento Commerce
- 2.2.0, 2.2.2, 2.2.3
How to apply the patch
We strongly recommend applying and testing the patch on the Integration/Staging environment, before applying it Production. We also recommend to have a recent backup before any manipulations.
How to apply this patch for Magento Commerce Cloud
- If you do not have a directory named
m2-hotfixesin the project root, please create one. - Copy the
MDVA-8371_EE_2.2.1_COMPOSER_v2.patchfile to them2-hotfixesdirectory. -
Add, commit, and push your code changes:
git add -A && git commit -m "Apply MDVA-8371_EE_2.2.1_COMPOSER_v2 patch" && git push origin
How to apply this patch for Magento Commerce
- Upload the patch to your Magento root directory.
- Run the following SSH command:
(If the above command does not work, try usingpatch -p1 < MDVA-8371_EE_2.2.1_COMPOSER_v2.patch-p2instead of-p1) - For the changes to be reflected, refresh the cache in the Admin under System > Cache Management.
Useful links
Apply custom patches to Magento Commerce (Cloud)