Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

With dispersed computation and parallel data flow between nodes, Fiorano Peers scale naturally and seamlessly with the addition of new Peer nodes and Enterprise Services across the network. Information and data flowing between distributed services does not have to pass through a central hub because each Fiorano Peer incorporates a JMS-compliant messaging server, allowing direct Peer-to-Peer connections to be set up on-the-fly between any set of Peers across the network. This on-demand creation of Peer-to-Peer data-flow connections is unique to the Fiorano platform and enables linear scalability and performance as new peers are added to the system. Furthermore, since peers can be hosted on existing (already reasonably powerful) hardware at the end-point of the network, enterprises do not have to purchase expensive hardware each time if there is an increase in performance requirements.

Server-

...

level Load Balancing

Load balancing is supported at the service level as well as the server levels.

...

By default, a service component is single threaded, that is, there is only one document being processed by a service component at any given point of time. If the CPU is not being fully utilized during a load test, then the performance and throughput can be increased by increasing the # number 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 in the Properties window for the Input Port of components.

Always start off While optimizing threads in this manner, always begin 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 the data flowing through the Event Process.


Figure 1: Input port properties of DB component with number of sessions set to '5'


Tip

Refer the Load Balancing section for service-level load balancing by distributing load across multiple Service Instances.

Adaptavist ThemeBuilder EngineAtlassian Confluence