You are currently reviewing an older revision of this page.
The purpose of this article is to look at the areas that an Appian Cloud customer can reduce their memory footprint on a site. In addition, it also highlights some strategies to optimize and control memory usage in Appian environments.
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 indicates a high number 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 indicates 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.
MySQL is used for both the primary and secondary data sources in Appian.
MySQL memory is allocated in order to do read and write operations with the database. High MySQL memory can be caused by complex or inefficient commands (such as large select statements or expensive views). In order to optimize MySQL memory, Appian Support recommends revisiting the way the database is being utilized and looking for ways in which it could be used more efficiently.
The application server is used for imports, exports, SAIL evaluation, emails, plugins, web services, and appserver sessions to services and users.
There are various internal processes that run to make sure that Appian is running smoothly. These include processes to store and replicate data, antivirus, and engine management and syncing software. Work with Appian Technical Support to resolve memory issue relaled to these components.
As your application grows and as Appian adds new features, your site will 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.