| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Throughput
|
The number of search requests successfully completed by the Endeca search engine
|
Number |
A high value is desired for this measure.
|
| Queue_length_avg
|
The average number of search queries waiting in the queue to be processed by the Endeca
|
Number |
Ideally, this value of this measure should be low. A high value could indicate a processing bottleneck on the server.
|
| Threads_busy_avg
|
The average number of threads that are busy processing search queries
|
Number |
This measure is a good indicator of the workload on the server.
|
| Total_processing_time_avg
|
The average time taken by the Endeca to process the search queries
|
Ms |
Ideally, the value of this measure should be low. A high value indicates that the engine is taking too long a time to process the search queries. Further investigation is required to isolate the root-cause of the processing bottleneck.
|
| Time_in_queue_avg
|
The average time that search queries spent in the queue before being processed by the Endeca server
|
Ms |
Ideally, the value of this measure should be low. A high value indicates that requests are being processed too slowly by the server, thus forcing requests to remain in the queue for too long a time. The bottleneck should be identified quickly and cleared.
|
| Time_in_dgraph_avg
|
The average time that queries spent in the dgraph
|
Ms |
|
| Time_sending_data_avg
|
The average time spent by the Endeca in sending the result data
|
Ms |
Whenever a slowdown is noticed in the Endeca, you may want to compare the value of the Time_in_dgraph_avg measure with that of this measure to determine where exactly the query spent too much time - in the dgraph? or in sending the result set?
|
| Records_in_resultset_avg
|
The average number of records found in the resultset of search query responses
|
Number |
|
| Response_size_avg
|
The average size of query response datas
|
Number |
|