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.
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.
In most situations, Appian Technical Support recommends updating the design to avoid using constants and moving/writing the value to a database instead.
This article applies to all versions of Appian.
Last Reviewed: February 2018
© 2019 Appian. All rights reserved.