KB-1226 Content (collaboration) engine consumes high memory

Maggie Deppe-Walker — Mon, 03 Jul 2023 02:54:01 GMT

Current Revision posted to Appian Knowledge Base by Maggie Deppe-Walker on 7/3/2023 2:54:01 AM

Symptoms

The Content (Collaboration) engine's database process occupies high memory on RAM when compared to the size of the .kdb file on disk. The general rule of thumb is that the .kdb files should consume roughly 2.5 times the amount of RAM as they do disk space, in gigabytes.

Cause

This issue is usually caused by a large number of versions of a single constant, which increases the memory footprint of the Content engine and can also cause slowness.

Action

Download and install the latest version of Content Tools.
Run the following command to identify all objects with 100+ versions getContentObjectsWithNumOfVersions(100,all,true).
1. Note: Only run this off-hours on production systems to avoid potential user impact.
Export, delete, and re-import all objects in the list to clear out excessive versions.
Restart Appian to reclaim memory.
For each constant identified with too many versions, update the application to stop creating new versions:
1. Search the constant's dependents in Appian Designer to find the process model where the constant is updated.
2. Update the Update Constant Smart Service to not create versions by setting input Create New Version: false.
3. Alternatively, if the constant is just used as an incrementing counter, use the Increment Constant Smart Service instead, which does not create versions.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2023

Tags: administration, memory, engines, application design, content

KB-1226 Content (collaboration) engine consumes high memory

Parmida Borhani — Sun, 05 Jan 2020 23:43:26 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 1/5/2020 11:43:26 PM

Symptoms

The Content (Collaboration) engine's database process occupies high memory on RAM when compared to the size of the .kdb file on disk. The general rule of thumb is that the KDB files should consume roughly 2.5 times the amount of RAM as they do disk space, in gigabytes.

Cause

This issue is usually observed when you have a large number of versions of a single constant, which increases the memory footprint of the Content engine's database process.

This issue can also occur when using the "Update Constant Smart Service", which creates new versions of a constant every time it's run. This creates a lot of versions of a constant over time.

Action

Download and install the latest version of Content Tools.
Import community.appian.com/.../5314.Rule_5F00_Constant-Version-Analysis.zip into your environment. This app was built in Appian 7.8 and will work in Appian 7.8 and later.
Run the Analyze Rule and Constant Versions action in the Rule/Constant Version Analysis application.
1. Under Constant or Rule, select Both.
2. Under Minimum Number of Versions, select 100. Appian Technical Support may request this number to be lower depending on how many objects there are.
3. Hit Submit.
Analyze the CSV file provided at the end of the action. Export, delete, and re-import all objects in the list.
Restart Appian to reclaim memory.

In most situations, Appian Technical Support recommends updating the design to avoid using constants and moving/writing the value to a database instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: administration, memory, engines, application design, content

KB-1226 Content (collaboration) engine consumes high memory

Nick Vigilante — Thu, 22 Feb 2018 09:10:12 GMT

Revision 5 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2018 9:10:12 AM

Symptoms

Cause

This issue is usually observed when you have a large number of versions of a single constant, which increases the memory footprint of the Content engine's database process.

This issue can also occur when using the "Update Constant Smart Service", which creates new versions of a constant every time it's run. This creates a lot of versions of a constant over time.

Action

Download and install the latest version of Content Details by UUID.
Import community.appian.com/.../5314.Rule_5F00_Constant-Version-Analysis.zip into your environment. This app was built in Appian 7.8 and will work in Appian 7.8 and later.
Run the Analyze Rule and Constant Versions action in the Rule/Constant Version Analysis application.
1. Under Constant or Rule, select Both.
2. Under Minimum Number of Versions, select 100. Appian Technical Support may request this number to be lower depending on how many objects there are.
3. Hit Submit.
Analyze the CSV file provided at the end of the action. Export, delete, and re-import all objects in the list.
Restart Appian to reclaim memory.

In most situations, Appian Technical Support recommends updating the design to avoid using constants and moving/writing the value to a database instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2018

Tags: memory, engines, application design

KB-1226 Content (collaboration) engine consumes high memory

Nick Vigilante — Thu, 22 Feb 2018 09:06:22 GMT

Revision 4 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2018 9:06:22 AM

community.appian.com/.../Rule_5F00_Constant-Version-Analysis.zipSymptoms

Cause

This issue is usually observed when you have a large number of versions of a single constant, which increases the memory footprint of the Content engine's database process.

This issue can also occur when using the "Update Constant Smart Service", which creates new versions of a constant every time it's run. This creates a lot of versions of a constant over time.

Action

Download and install the latest version of Content Details by UUID.
Import community.appian.com/.../5700.RuleConstant-Version-Analysis.zip into your environment. This app was built in Appian 7.8 and will work in Appian 7.8 and later.
Run the Analyze Rule and Constant Versions action in the Rule/Constant Version Analysis application.
1. Under Constant or Rule, select Both.
2. Under Minimum Number of Versions, select 100. Appian Technical Support may request this number to be lower depending on how many objects there are.
3. Hit Submit.
Analyze the CSV file provided at the end of the action. Export, delete, and re-import all objects in the list.
Restart Appian to reclaim memory.

In most situations, Appian Technical Support recommends updating the design to avoid using constants and moving/writing the value to a database instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: memory, engines, application design

KB-1226 Content (collaboration) engine consumes high memory

Nick Vigilante — Tue, 07 Mar 2017 14:11:39 GMT

Revision 3 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 2:11:39 PM

Symptoms

Cause

This issue is usually observed when you have a large number of versions of a single constant, which increases the memory footprint of the Content engine's database process.

This issue can also occur when using the "Update Constant Smart Service", which creates new versions of a constant every time it's run. This creates a lot of versions of a constant over time.

Action

Download and install the latest version of Content Details by UUID.
Import community.appian.com/.../5700.RuleConstant-Version-Analysis.zip into your environment. This app was built in Appian 7.8 and will work in Appian 7.8 and later.
Run the Analyze Rule and Constant Versions action in the Rule/Constant Version Analysis application.
1. Under Constant or Rule, select Both.
2. Under Minimum Number of Versions, select 100. Appian Technical Support may request this number to be lower depending on how many objects there are.
3. Hit Submit.
Analyze the CSV file provided at the end of the action. Export, delete, and re-import all objects in the list.
Restart Appian to reclaim memory.

In most situations, Appian Technical Support recommends updating the design to avoid using constants and moving/writing the value to a database instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: memory, engines, application design

KB-1226 Content (collaboration) engine consumes high memory

Nick Vigilante — Tue, 07 Mar 2017 10:09:15 GMT

Revision 2 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 10:09:15 AM

Symptoms

Cause

This issue is usually observed when you have a large number of versions of a single constant, which increases the memory footprint of the Content engine's database process.

This issue can also occur when using the "Update Constant Smart Service", which creates new versions of a constant every time it's run. This creates a lot of versions of a constant over time.

Action

Download and install the latest version of Content Details by UUID.
Import community.appian.com/.../2514.RuleConstant-Version-Analysis.zip into your environment. This app was built in Appian 7.8 and will work in Appian 7.8 and later.
Run the Analyze Rule and Constant Versions action in the Rule/Constant Version Analysis application.
1. Under Constant or Rule, select Both.
2. Under Minimum Number of Versions, select 100. Appian Technical Support may request this number to be lower depending on how many objects there are.
3. Hit Submit.
Analyze the CSV file provided at the end of the action. Export, delete, and re-import all objects in the list.
Restart Appian to reclaim memory.

In most situations, Appian Technical Support recommends updating the design to avoid using constants and moving/writing the value to a database instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: memory, engines, application design

KB-1226 Content (collaboration) engine consumes high memory

Nick Vigilante — Mon, 06 Mar 2017 21:39:44 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 3/6/2017 9:39:44 PM

Symptoms

Cause

This issue is usually observed when you have a large number of versions of a single constant, which increases the memory footprint of the Content engine's database process.

This issue can also occur when using the "Update Constant Smart Service", which creates new versions of a constant every time it's run. This creates a lot of versions of a constant over time.

Action

Download and install the latest version of Content Details by UUID.
Import community.appian.com/.../5633.RuleConstant-Version-Analysis-2.6.0.zip into your environment. This app was built in Appian 7.8 and will work in Appian 7.8 and later.
Run the Analyze Rule and Constant Versions action in the Rule/Constant Version Analysis application.
1. Under Constant or Rule, select Both.
2. Under Minimum Number of Versions, select 100. Appian Technical Support may request this number to be lower depending on how many objects there are.
3. Hit Submit.
Analyze the CSV file provided at the end of the action. Export, delete, and re-import all objects in the list.
Restart Appian to reclaim memory.

In most situations, Appian Technical Support recommends updating the design to avoid using constants and moving/writing the value to a database instead.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: memory, engines, application design