Best Practices to Optimize Workflow Editing Speed

Comments

3 comments

  • Avatar
    Adrian Williams

    A support ticket has been raised to enables us to discuss this in more detail.

     

    0
    Comment actions Permalink
  • Avatar
    Don Graham

    Is there any information that can be shared with the community on this? No one I work with has had the delays that are mentioned above however users do complain about the latency compared to how Lavastorm ran.

    0
    Comment actions Permalink
  • Avatar
    Adrian Williams

    If the data flow contains many nodes then, in general, the design-time responsiveness of the UI may be improved if Composites are used to group related nodes as there are fewer nodes to render on the canvas in any one 'level'.

    In the case where Run Dependencies (Clocks) are not used the Composites are only graphical objects that do not affect the run-time performance of the individual nodes. When changes are made to the data flow, the use of Composites restricts the scope of work required by the system to reflect those changes - which will decrease the time required to compose the data flow model.

    When Run Dependencies are used to synchronize the running of two Composites (A & B) and the Composites each contain a large number of nodes (#m, #n) then the would be n * m implicit Run Dependencies created which may degrade performance. I this situation it is recommended that explicit run dependencies are made to nodes within each of the composites or that a Run Dependency is created between, say, Composite A and a single node and a separate Run Dependency is created between the single node and Composite B - which would result in the creation of n + m Run Dependencies.

    The Help documentation provides information on how explicit Run Dependencies can be created for nodes within Composites

    Some suggested tips are:

    • Group nodes for each input data source into its own Composite
    • Group logical strings of nodes for transformation and analysis into their own Composites
    • Multiple output sources should have their own Composites
    • Improve the readability of the data flow by keeping the number of nodes on a level to a relatively small number that can be viewed without the need to pan the canvas, say around 20
    • Add names to your nodes and Composites - this will make any error messages more readable. You can now navigate directly to an errored node by clicking on the error in the error panel - the canvas will pan to the node; if the node is on another level to the current displayed level, the canvas navigation will drill-in/out and pan to the node.
    0
    Comment actions Permalink

Please sign in to leave a comment.



Powered by Zendesk