The purpose of this article is to outline how an Appian Cloud customer can reduce the memory footprint of a site.
Table of Contents:
The process execution and process analytics engines store data on processes running in Appian (such as process variables and process history).
How to Optimize
Run an Appian Health Check to identify which processes are taking up the most memory. After identifying the largest consumers you can take several actions depending on the results:
The content engine stores metadata and security for communities, knowledge centers, folders and documents as well as rules/interfaces, constants and data stores.
High content engine memory may indicate a high number of versions of constants or document metadata. To optimize, Appian Support recommends cleaning up constant versions. Review KB-1226 for more details.
The design engine stores all of the process models and data types.
High design engine memory may indicate a high number of process model versions in the cloud environment. To optimize, Appian Support recommends looking into cleaning up process model versions either manually or by leveraging the Process Model Utilities plugin from the AppMarket.
select table_schema, table_name, table_rows, avg_row_length, data_length, index_length from information_schema.tables order by data_length desc;
As your applications grow and as Appian adds new features, your site may require more RAM to meet the increased memory demands. If optimizing memory in the components listed above has not reduced memory below our monitoring thresholds and Appian Support continues to create cases to alert you of high memory, you must upgrade hardware to reduce the risk of your site crashing and potential data loss. Please speak with your account executive to increase the memory allocation for your site.
This article applies to all versions of Appian Cloud.
Last Reviewed: September 2020
© 2020 Appian. All rights reserved.