Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: Tim MeagherHi,
This is exactly what happens if you have multiple threads connected to the server and are using streaming mode & the external controller.
I'll have to check, but I think that streaming might only be supported on enterprise server (unix) installations.
However, if you're connected to such a server, in Tools->Preferences->Server Farms, you can configure your farm and set the Controller to External, and the Scheduler to streaming.
In streaming mode, if there are enough available threads on the server to execute multiple nodes, then:
- If there is a node A, which takes only one input, and
- This node is connected to the output of a node B, and this output is only wired from B to A (not to any other nodes)
Then the server will attempt to stream the data through from node B to node A, meaning that node A can start before B terminates.
In some cases, the downstream node (A) is forced to wait until the predecessor node is complete because it needs to operate on all of the data before it can do anything sensible (for example a sort node).
However, in the case of things like filters, splits etc, and the head node, the downstream node can operate on the data and send the data through to the next node.
This means that the node further downstream than the Head node can being processing prior to the completion of the node that occurs before the Head node.
Tim.