Which option is NOT recommended for reducing memory usage when storing large data in process variables?

Which option is NOT recommended for reducing memory usage when storing large data in process variables?

• A. Splitting the process into sub processes.
• B. Reducing the number of process variables.
• C. Storing large data chunks directly in process variables.
• D. Compressing text before storing

Answer: (C)

Managing memory in Appian when dealing with large data involves keeping only what’s needed in the process scope. Process variables stay in memory for the life of the process, so putting large chunks of data directly into them tends to bloat memory usage and can degrade performance. The best approach to keep memory lean is to isolate work into sub-processes, which confines data lifetimes and enables earlier cleanup. Reducing the number of process variables cuts the overhead of maintaining many names and values. Compressing text before storing reduces the amount of data held in memory. Storing large data chunks directly in process variables runs counter to these strategies and leads to higher memory consumption.

Managing memory in Appian when dealing with large data involves keeping only what’s needed in the process scope. Process variables stay in memory for the life of the process, so putting large chunks of data directly into them tends to bloat memory usage and can degrade performance. The best approach to keep memory lean is to isolate work into sub-processes, which confines data lifetimes and enables earlier cleanup. Reducing the number of process variables cuts the overhead of maintaining many names and values. Compressing text before storing reduces the amount of data held in memory. Storing large data chunks directly in process variables runs counter to these strategies and leads to higher memory consumption.