KB-1248 How to address high memory usage in self-managed Appian environments

pauline.delacruz — Mon, 24 Nov 2025 20:05:54 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 11/24/2025 8:05:54 PM

This article details root causes as well as corrective actions to be taken in situations where an Appian environment is experiencing higher than normal memory usage. In addition, some strategies to optimize and control memory usage in Appian environments are also listed.

Managing high memory usage

Using the Task Manager (Windows) or the top command (Unix) and making sure that the command path is enabled, review the currently active OS processes sorted by individual memory usage and identify one or more processes consuming the most memory. In Appian environments specifically, the top memory consumers are usually those that are listed below:

Application Server

An increase in memory usage for the java process of the application server can indicate a potential memory leak. Review the system.csv file to analyze the heap used vs. heap available for an increasing trend. A heap dump is also helpful to detect a leak as well as its root cause. Steps to collect a heap dump can be found in KB-1176.

Apart from the heap space, a leak may also occur in the metaspace region. Typically this happens due to excessive class loading or a large number of static imports from custom plug-ins. Use jmap -histo <JAVA_PROCESS_ID> and jmap -clstats <JAVA_PROCESS_ID> to get information on class loader statistics to determine if this is the case.

Note: Running jmap -clstats <JAVA_PROCESS_ID> should be performed during off-peak business hours during a scheduled outage. Running this command locks the class loader in the application server and renders it unresponsive while the command is executing.

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

An increase in search server memory usage can be caused due to excessively large frequency of rule executions within the environment. This may be alleviated either partially or completely by recreating the search indices. Steps on how to do this can be found in the action section of KB-1082. If there is no significant reduction then this increase may be legitimate. In such cases, consider re-sizing the search server.

Engines

For each of the k processes in the process list, review the command path to identify the corresponding engine. Several cleanup activities may be required depending on which engines are experiencing high memory usage.

Important:

Proceed with caution when performing any cleanup activities described below. Ensure that any objects or versions are truly no longer needed before removing them. Contact Appian Technical Support if you have questions or encounter any issues during the process.

A restart of the environment is required after cleanup operations to release freed memory and obtain accurate current memory usage.

Process Execution Engines (adb pe)

Memory usage for the execution engines is tied to the total number of process instances in the environment, including:

Running processes
Completed processes
Inactive or stale processes
Unarchived historical processes

All of these remain loaded in execution-engine memory until they are archived or deleted.

Recommended Cleanup Actions

Review and clean up process instances by archiving or deleting those that are no longer needed.
Use the Appian Health Check report specifically the Sizing section to identify:
- Process models that generate large volumes of instances
- Processes with unusually large memory footprints
- Areas where process cleanup will have the greatest impact

Memory Impact of Process Variables

Execution-engine memory is also heavily affected by the size of process variables (PVs). Appian allocates memory based on the values of PVs even for completed processes that have not yet been archived.

Best Practices:

Avoid storing large strings (e.g., Base64-encoded data, large JSON/XML payloads) in PVs or node inputs.
Store large content in a document, database table, or external storage service instead.
Keep PVs small and structured where possible to minimize memory retention.

Process Analytics Engines (adb pa)

The analytics engines maintain aggregated data for process instances, so their memory usage is typically correlated with the execution engines.

Recommended Approach

Perform cleanup on execution-engine processes first (archive/delete).
Review the Health Check report for analytics-related findings (e.g., oversized analytics caches or unusually large process volumes).
Perform an Analytics Reset.
- This is a key step in releasing stale analytics data and rebuilding the analytics indexes.
- An analytics reset typically reduces PA engine memory significantly once underlying process data has been cleaned up.

If memory usage remains high after cleanup and an analytics reset, contact Appian Technical Support for deeper analysis or specialized cleanup operations.

Process Design Engine

The design engine is the process of type adb pd. A high memory on this engine indicates a large number of design objects such as data types or process models and their versions. A cleanup of these objects is the best way to bring down the memory usage for this engine.

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.

Note: Process model versions should only be deleted in non-production environments where processes are seldom or never unarchived. If you attempt to unarchive a process for a version of a process model that doesn't exist in this engine and if there are no running instances of that process model for that specific version, then you will be unable to successfully unarchive that process.

Collaboration Engine

For the collaboration engine adb dc, the cleanup needs to be done for content objects (e.g., rules or constants) and their versions. More information on the possible causes can be found in KB-1226.

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

It is also rare for these two processes adb n and adb s to use an excessively large amount of memory, however this can happen when there are a large number of alerts in the environment for one or more users. Should this be the case, contact Appian Technical Support to coordinate the necessary actions to bring the size of these engines down.

Collaboration Statistics Engine

It is unusual for collaboration statistics adb stat to consume a large amount of memory but this can happen due to a large frequency of document downloads. To coordinate the necessary cleanup operations to reduce the memory usage for this engine, contact Appian Technical Support.

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2025

Tags: self-managed, administration, memory, how-to

KB-1248 How to address high memory usage in self-managed Appian environments

pauline.delacruz — Thu, 02 Nov 2023 21:23:49 GMT

Revision 16 posted to Appian Knowledge Base by pauline.delacruz on 11/2/2023 9:23:49 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

For k processes in the process list, review the command path to identify the corresponding engine. There are a number of cleanup activities to be done depending on which engines are experiencing high memory usage.

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.

Process Execution Engines

Processes with adb pe in the command path correspond to the execution engines. A cleanup (archiving or deleting) of processes in the environment is the best way to reduce memory usage for these engines. Use the sizing section of the health check report to identify Appian processes that have the highest resource consumption.

As a best practice, avoid saving long strings (such as base64 encoded strings) as process variables or node inputs. These long strings consume execution engine memory. Instead, consider saving the strings to a database or call a web service and save the strings as documents.

Process Analytics Engines

Processes of type adb pa are the analytics engines. In most cases, analytics size is linked to execution engines so this is typically addressed by following the above steps for execution engines followed by an Analytics reset.

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2018

Tags: self-managed, administration, memory, how-to

KB-1248 How to address high memory usage in self-managed Appian environments

Maggie Deppe-Walker — Fri, 29 Sep 2023 03:25:13 GMT

Revision 15 posted to Appian Knowledge Base by Maggie Deppe-Walker on 9/29/2023 3:25:13 AM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2018

Tags: self-managed, administration, memory, how-to

KB-1248 How to address high memory usage in self-managed Appian environments

Parmida Borhani — Tue, 29 Sep 2020 03:07:20 GMT

Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 9/29/2020 3:07:20 AM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2018

Tags: self-managed, administration, memory, how-to

KB-1248 How to address high memory usage in self-managed Appian environments

Parmida Borhani — Thu, 10 May 2018 22:10:57 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 5/10/2018 10:10:57 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2018

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Parmida Borhani — Thu, 10 May 2018 22:09:41 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 5/10/2018 10:09:41 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Nick Vigilante — Wed, 29 Nov 2017 08:23:59 GMT

Revision 11 posted to Appian Knowledge Base by Nick Vigilante on 11/29/2017 8:23:59 AM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Parmida Borhani — Tue, 28 Nov 2017 17:39:07 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 5:39:07 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Parmida Borhani — Tue, 28 Nov 2017 17:35:38 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 5:35:38 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Parmida Borhani — Tue, 28 Nov 2017 17:33:35 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 5:33:35 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Parmida Borhani — Tue, 28 Nov 2017 17:32:08 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 5:32:08 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Parmida Borhani — Thu, 09 Nov 2017 22:31:32 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 11/9/2017 10:31:32 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Nick Vigilante — Tue, 24 Oct 2017 11:03:34 GMT

Revision 5 posted to Appian Knowledge Base by Nick Vigilante on 10/24/2017 11:03:34 AM

Managing high memory usage

Application Server

Note: Running jmap -clstats <JAVA_PROCESS_ID> should be performed during off-peak business hours during a scheduled outage. Running this command locks the cloassloader in the application server and renders it unresponsive while the command is executing.

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Nick Vigilante — Thu, 01 Jun 2017 15:51:04 GMT

Revision 4 posted to Appian Knowledge Base by Nick Vigilante on 6/1/2017 3:51:04 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Nick Vigilante — Fri, 17 Mar 2017 16:13:37 GMT

Revision 3 posted to Appian Knowledge Base by Nick Vigilante on 3/17/2017 4:13:37 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

If you went through all the steps in this KB article but the system is still running high on memory, feel free to add additional memory to the system.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, memory, how-to

KB-1248 How to address high memory usage in on-premise Appian environments

Nick Vigilante — Mon, 06 Mar 2017 22:47:24 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 3/6/2017 10:47:24 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, memory

KB-1248 How to address high memory usage in on-premise Appian environments

Nick Vigilante — Mon, 06 Mar 2017 17:47:37 GMT

Revision 2 posted to Appian Knowledge Base by Nick Vigilante on 3/6/2017 5:47:37 PM

Managing high memory usage

Application Server

If there are no memory leaks then the increase may be due to legitimate activity on the environment.

Search Server

Engines

A restart of the environment is required after cleanup operations to release the freed up memory and obtain the current memory usage accurately.

Process Execution Engines

Process Analytics Engines

If the high memory usage persists, contact Appian Technical Support for assistance.

Process Design Engine

Collaboration Engine

In addition to a manual cleanup, Appian Technical Support may be able to assist with identifying and removing objects and/or versions in bulk.

Notification & Notification Email Engines

Collaboration Statistics Engine

Other Appian Processes

For any other another Appian process(es) consuming an unusually large amount of RAM, contact Appian Technical Support for assistance.

Optimizing Appian memory usage

Some strategies to proactively control memory usage of Appian environments are listed below:

Creating Memory Efficient Models to improve overall performance: Creating Memory Efficient Models
Setting the load metric property to limit the growth of execution engines: MAX_EXEC_ENGINE_LOAD_METRIC
Optimizing reports to control analytics engines memory usage: Report Performance Details
Setting appropriate JVM arguments (particularly the "Xmx") to ensure the application server doesn't use more memory than what's required.
Implementing appropriate auto archival/auto deletion policies for process instances: Archiving Processes

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, memory, how-to