This article details root causes as well as corrective actions to be taken in situations where an Appian Cloud environment is experiencing higher than normal memory usage. In addition, some strategies to optimize and control memory usage in Appian environments are listed. In Appian Cloud environments specifically, the top memory consumers are usually those that are listed below:
Note: Proceed with caution when exercising any of the cleanup activities described. Ensure that any objects/versions are in fact no longer needed or used before removing them. Reach out to Appian Technical Support for any questions or issues at any stage.
A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.
A cleanup of processes in the environment is a good way to reduce memory. Appian Support also recommends reviewing your Data Management settings and configuring your process models appropriately. You may use the sizing section of the health check report to identify Appian processes that have the highest resource consumption. Ensure you have the most current version of the Appian Health Check plugin installed.
Some design objects such as data types and process models can consume high memory. While data types and process models need to be cleaned up manually, process model versions can be deleted in bulk using the Process Model Utilities shared component. In general, the recommendation is not to have more than 100 versions per process model.
"Warning: This smart service should be executed over versions you don't have running instances on. You can use a process model report to determine whether you can safely delete versions or not. The reason being this will delete the process models definitions from the file system as well, which are used by running instances. Make sure you delete only those versions from which you no longer have process instances running. This also applies to archived instances. If you intend to unarchive process instances, then we recommend against using this approach for those particular models you foresee unarchiving in the future."
Rules and constants will occasionally need to be cleaned up. More information on the possible causes can be found in KB-1226. Please follow the steps in the action section of this article and let Appian Technical Support know when it has been completed. The site will need to be restarted to reclaim memory.
Some strategies to proactively control memory usage of Appian environments are listed below:
If all steps in this article were followed and memory still runs high on the machine in question, then additional resources may be purchased to increase the hardware on the machine. Please speak with your account executive for more details.
This article applies to all versions of Appian.
© 2019 Appian. All rights reserved.