search cancel

Need to have performance improvement when using a Master Javelin flow as it calls 40 or more child flows.


Article ID: 190459


Updated On:


CA Test Data Manager (Data Finder / Grid Tools)


Need a method to enhance performance when a Master Flow calls many child flows - for instance 40 or more.


Release : 4.7

Component : CA Test Data Manager


The fix for this issue is found in Javelin-

After installing Javelin, update the configuration EnableThreadLaunchCallJavelin to True in the below config files (assuming Javelin is installed in the default path):
C:\Program Files\Grid-Tools\Javelin\Javelin.exe.config
C:\Program Files\Grid-Tools\Javelin\JavelinExecutor.exe.config

The flows "MasterFlow".vwf and "ChildProcessFlows".vwf are updated to log the SubFlowExitCode
The new feature allow a parent flow to call a child flow within the same process. The customer in question has a large number of child flows (more than 40 child flows ).When EnableThreadLaunchCallJavelin is false then it is the default behaviour which is to start a new process for each child subflow.

Performance will be an issue when calling so many child subflows. As subflows were run by a separate JavelinExecutor process, each subflow would consume a set of cursors. However as we moved to using threads to improve performance, one single process will handle the masterflow and all the subflows requiring a higher number of cursors. The DBAs will need to change the max cursor setting to a larger value in order to handle the increased number of cursors for the child processes.