Json size and performances #585
-
|
Hello, I integrated Conductor into our traceability solution to run business rules, it works like a charm, until the number of nodes processed in a workflow reached a limit. In some loops for example, I have more than 1000 iterations sometimes, and the loop json output is getting extra huge, slowing down the execution as it goes. Is there a way to prevent this and avoid the full output of all tasks into a loop to be reproduced in the loop output ? I checked into the docs but with no luck. Thanks for your answers ! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Using keepLastN in the inputParameters of the DO_WHILE task make the trick (use value -2 to keep nothing as value 0 keeps 2 iteration output). |
Beta Was this translation helpful? Give feedback.
Using keepLastN in the inputParameters of the DO_WHILE task make the trick (use value -2 to keep nothing as value 0 keeps 2 iteration output).