Setting Application Component Criteria

Click the Magnify icon to view the NAS Administrator.


Application Component criteria allow administrators to set load- balancing factors to consider the performance of running components and balance component considerations with server load.

Server Load

This value sets the importance of Application Component criteria versus server load when evaluating the overall load of the NAS. Server load and the four Application Component criteria must total 100%. For example, if the server load bar is set to zero (far left) then the Server Load settings are not considered at all. If the server load bar is set to 100% (far right) then the Application Component criteria is not considered when the NAS evaluates its load information.

Cached Results Available

For each Application Component this server can process, this value considers if the results are cached on the server. Weight this value if the cache can be reused by new incoming requests. Keep in mind that Application Components that have many personalized modifications or security restrictions cannot reuse the cached results.

Lowest Average Execution Time

The server evaluates how long specific Application Components take to execute. Based on the broadcast of all the NAS, requests go to the server that broadcasts the fastest execution time for that Application Component.

Most Recently Executed

The server that last executed a given Application Component. Weight this value when your best choice is to execute the request on the same server that the request ran on. The main reason for weighting this value is because the server might have cached results for an Application Component and can therefore return results quickly.

Fewest Executions

For each Application Component, this value relates to the number of times Application Component requests were allocated to that NAS. When all the broadcasts are evaluated, the NAS that was allocated the fewest requests (and therefore showing the fewest executions) is evaluated as the best choice. Weight this value heavily when you want to distribute the requests equally among all servers in the enterprise.