Which of the following is NOT a recommended way to reduce the memory footprint of a process model?

Which of the following is NOT a recommended way to reduce the memory footprint of a process model?

• A. Split the process into sub processes so that only part of the overall process is active.
• B. Reduce the number of process variables.
• C. Do not store large data chunks like text strings in process variables.
• D. Store large data chunks like text strings in process variables.

Answer: (D)

Managing memory footprint in a process model hinges on keeping in-memory data small and loaded only as needed. Splitting the process into sub-processes helps because only the active portion consumes memory at a given moment, rather than the entire long-running flow. Reducing the number of process variables lowers the amount of data held in memory for each running instance. Avoid storing large data chunks directly in process variables because those variables stay in memory for the life of the process instance; large strings or blocks increase memory usage and can slow down execution. Instead, store big data externally (in a database or file/content store) and keep lightweight references in the process variables, loading or streaming data only when required. This approach keeps memory usage predictable and scalable.

Managing memory footprint in a process model hinges on keeping in-memory data small and loaded only as needed. Splitting the process into sub-processes helps because only the active portion consumes memory at a given moment, rather than the entire long-running flow. Reducing the number of process variables lowers the amount of data held in memory for each running instance. Avoid storing large data chunks directly in process variables because those variables stay in memory for the life of the process instance; large strings or blocks increase memory usage and can slow down execution. Instead, store big data externally (in a database or file/content store) and keep lightweight references in the process variables, loading or streaming data only when required. This approach keeps memory usage predictable and scalable.