...
The Distributed Process model implemented by the Fiorano Platform automatically ensures that as many operations as possible are run in parallel. The data flows between applications are represented by graphs, and all independent trees within the application graph represent concurrent computations. Within a single tree, operations are implicitly serialized based on in-built data-flow dependencies.
Scalability is critical to ensure that the platform scales both with current projects (likely in themselves to be highly distributed, probably across company boundaries) and with future growth. The Fiorano platform addresses scalability issues as follows:explained in the below sections.
Transparent Resource Addition
...
By default, a service component is single threaded, that is, there is only one document being processed by a service component at any given time. If the CPU is not being fully utilized during a load test, then the performance and throughput can be increased by increasing the # of sessions (that is, threads) for a component. This linearly increases the number of data - elements being processed by the component concurrently. The number of threads per component can be set within in the Properties window of for the InPort of each component in the StudioInput Port of components.
Always start off with the bottleneck component when optimizing threads this way since there will typically be only one bottleneck component in a given process at a time. Once the first bottleneck component is fixed, the bottleneck typically moves to another component in the flow. This technique helps optimizing the number of sessions/threads for each component based on the ability of the hardware to process data flowing through the Event Process.
Figure 1: INPORT Properties panelInput port properties of DB component with number of sessions set to '5'