Performance optimization for Job Stream GUI and Job Stream execution

Current Situation

• The job stream GUI is slow when using many jobs in a job stream. The reason for this is, that reading the data for the job stream joins data from different database tables to a single result set. This join operation is executed by the Hibernate persistence layer with a single select statement for the leading table and n select statements for each record to get the data from the second table.

Desired Behavior

• Displaying the graph of a job stream with 100 jobs should not take more than 5s.
• To achieve this, some optimizations should be implemented.
• Executing the join should be done by a single select statement.
• Statements to read the state for In Conditions should only be executed when displaying the job stream graph is expanded mode. This should not be performed when the job stream graph is collapsed as the data are not required.
• When a job stream instance is selected, only events for this instance should be considered during the initialization.

Patch

A patch for JOC Cockpit is available. Please download from here. Then apply the patch with the JOC Cockpit Patch Executor

Please clear your browser cache and restart JOC Cockpit.

The ensure that the patch is installed correctly click the rabbit in JOC Cockpit, It should display the release number:

JOC Cockpitc62f506898)9a4323fffd747be9c163884787a1a7
1.13.7-patch (2020-11-30)