eG Monitoring
 

Measures reported by FSFASTCntPluTest

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 measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
FSAvgCalBakTim Indicates the average time between acknowledgement of a batch submission and the receipt of a final success or failure callback in the FAST Search server. Millisec An abnormally high value for the Avg end-to-end time is an indication of a slowdown in the search engine. When this happens, you can compare the values of all the other measures to isolate where the slowdown occurred - did it occur before initialized items were placed for submission? did it occur after submitting batches for processing - if so, was it at the first attempt to submit? or what is when waiting for an acknowledgement for submission?
FSAvgEndTOEndTim Indicates the average time taken from item initialization to completion of indexing. Millisec
FSAvgIntTim Indicates the average time taken from an item initialization until the item has been placed into a batch for submission. Millisec
FSAvgSubTim Indicates the average time taken between submitting an item's batch in the first attempt to receiving an acknowledgment for the batch that has successfully been received for processing. Millisec
FSAvgWatTim Indicates the average time from when an item is placed into a batch until the first attempt to submit. Millisec
FSBatFail Indicates the number of batches that failed prior to indexing. Number Ideally, the value of this measure should be zero.
FSBatOpn Indicates the number of batches that are currently being processed. Number  
FSBatRea Indicates the number of batches received from the content sources that are queued up and are ready to be submitted to the Content Distributor. Number If the value of this measure is 0, it indicates that the FAST Search Server 2010 for SharePoint farm back-end is processing content faster than the Content SSA can crawl. This means that you can further increase your crawling rate. If the number is higher than zero, consider adding more document processors, or see whether you have added an external item processor that slows down the speed of certain items flowing through the indexing pipeline.
FSBatSub Indicates the number of batches that were sent to the FAST Search server but the callback is still pending. Number If the value of this measure is 0, it indicates that the batches are not sent to the Fast Search Server Farm backend for processing.
FSBatSuc Indicates the number of batches that were indexed successfully. Number  
FSBatTot Indicates the total number of items that were sent for processing through the Content SSA since the last service restart. Number  
FSItmsOpn Indicates the number of items that were currently being processed. Number  
FSItmsSuc Indicates the number of items that were indexed successfully. Number  
FSItmsTot Indicates the total number of items that were sent for processing through the Content SSA since the last service restart. Number