When users complain that their search queries are taking too long to execute and produce results, you can use the metrics of this test to figure out where the bottleneck is - is it because the FAST Search 2010 server is taking too long to perform indexing? if so, where is time being spent - while waiting for placing the items in a batch? while submitting batches of items for processing? while awaiting a success/failure acknowledgement for a batch submission? On the other hand, if indexing is not the bottleneck, then, could the slowdown have occurred because of too many batch failures? or because the server was overloaded with too many batch processing requests? or could the problem be owing to the slow crawling rate of the FAST Content SSA?

This page depicts the default parameters that need to be configured for the FSFASTCntPluTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.