Composite performance - Data360_Analyze - 3 - 3.12

Data360 Analyze Server Help

Product type
Product family
Data360 Analyze
Product name
Data360 Analyze
Data360 Analyze Server Help
First publish date

You may notice a performance degradation if there is a run dependency between two composites that each have a large number of contained nodes.

For example, you have ten nodes in composite A, and ten nodes in composite B. There is a wait dependency (clock) linking composites A and B, meaning that each node in composite B must wait for each node in composite A to execute before beginning their execution, giving a total of 100 wait dependencies:

Composite performance

You can improve the performance if you can reduce the number of dependencies. To reduce the number of dependencies, you can link to a single node between the two composites. In this example, this would reduce the total number of wait dependencies to twenty.

Composite performance

Additionally, if you have identified that only one, or a small number, of the contained nodes in composite A are required to complete before composite B starts, you can explicitly clock to these nodes within the composite:

  1. Drill into composite A.

    There are no input clocks or output clocks displayed, indicating that all nodes are clocked:

    Composite performance

  2. Select the node, or nodes, that you want to connect to the composite's output clock (in this example, the Cat node).
  3. Right-click and select Run Dependencies > Composite > Downstream Waits.

    The output clock is displayed and is linked to the selected node(s):

    Composite performance