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?

The default parameters associated with this test are:

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

• Specify the host for which the test is to be configured in the HOST text box.

• Specify the port on which the specified host listens in the PORT text box. By default, the port number is 54321.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.