The memory footprint of active processes is very larger and is potential issue g

Dhiraj Kumar over 7 years ago

The memory footprint of active processes is very larger and is potential issue going into production . Is there a pattern process that i can design to archive these objects and then resurrect the same ?

I am doing a direct comparison here to Java where in Serialized objects can be moved from heap space to the physical hard drive and hoping there is a process of a JMX hook in place to be able to do the same in Appian .

We are using 16.2

Discussion posts and replies are publicly visible

Parents

0 sanjays0006 over 7 years ago

Dhiraj,
What is major contributor of your memory foot print ?
Process History or Process Variables size or Activity Class Parameter size(I assume that these 3 are major factors for Memory foot print)
If Process History is the issue, then probably you should use hidden variables.
Else, you should design break process into smaller sub processes and then archive accordingly.

Are you using any custom plugins in this process model?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 sanjays0006 over 7 years ago

Dhiraj,
What is major contributor of your memory foot print ?
Process History or Process Variables size or Activity Class Parameter size(I assume that these 3 are major factors for Memory foot print)
If Process History is the issue, then probably you should use hidden variables.
Else, you should design break process into smaller sub processes and then archive accordingly.

Are you using any custom plugins in this process model?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data