Why High Memory Consumption for Backup Service during Automatic Backup on Liferay Cloud
Written By
Madhusudan Sharma
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- When an automatic backup is triggered by the system, the memory utilization (for backup service) is more than 80%. However, the backup service is working fine for both automatic and manual backups.
- If the memory utilization is high then is there any issue or it's normal?
Environment
- Liferay DXP 7.1
- Liferay DXP 7.2
- Liferay DXP 7.3
- Liferay DXP 7.4
Resolution
- The backup service internally runs as a node.js application, and it's crafted in a way to avoid memory and CPU exhaustion during its operations (creation, deletion, restore, etc).
- This service uses as much memory as it is given. If a maximum allowance of 1024MB is configured, it will use the same to optimize the file reading and writing.
- The backup service reads and writes to the File System during backup creation and restoration.
- The memory to be used for file caching probably depends on how many files are being read/written and the size of those files. Therefore an increase in backup size would directly increase the memory.
- Additionally, this (backup service memory) is a reclaimable memory and high utilization of it should not be a concern. Also, the non-evictable memory used by the node.js process itself is quite low.
Did this article resolve your issue ?