Endeca Hotspots Test
This test monitors the performance of specific features, such as clustering, record search, record filter, range filter, content spotlighting, and snippeting to help administrators proactively identify the hotspots and optimize them for improving the overall performance of the server.
Target of the test : An Endeca Search Application
Agent deploying the test : An internal agent
Outputs of the test : One set of results the Endeca search application being monitored.
Parameter | Description |
---|---|
Test period |
How often should the test be executed |
Host |
The IP address of the host for which this test is to be configured. |
Port |
The port at which the specified host listens to. The default port is 15000. |
PerfStatURL |
Specify the URL to access the page from which this test will be collecting the required statistics. The default URL will be in the format: http://{Endeca_Server_IP}:8000/admin?op=stats |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Total navigation/record search query time
|
Indicates the time taken to perform refinements calculations and keyword search functionality combined. |
Seconds |
A low value is desired for this measure. The detailed diagnosis of this measure indicates the Metrics time(seconds). |
Clustering time
|
Indicates the time taken for record clustering. |
Seconds |
Ideally, the value for this measure should be low. A high value for this measure can cause performance degradation in terms of latency. The detailed diagnosis of this measure indicates the Metrics time(seconds). |
Record filter time
|
Indicates the time taken to perform record filters. |
Seconds |
Record filters allows to define the total record sets into subsets and thereby restricting the search and navigation results to these subsets. A low value is desired for this measure. The detailed diagnosis of this measure indicates the Metrics time(seconds). |
Range filter time
|
Indicates the time taken to perform range filters. |
Seconds |
Range filters allows the selection of a subset of the entire data set for display and helps navigation queries to return the results from the specific subset of the dataset. Hence, the value of this measure should be low. |
Content spotlighting time
|
Indicates the time taken to apply Merchandising Rules, including sorting of Merch Rules results. |
Seconds |
The time taken for identification and promotion of contextually relevant results from the dataset to the users must be low. A high value can increase the navigation time and causes performance degradation. |
Dimension search time
|
Indicates the time taken for dimension search. |
Seconds |
Ideally, the value for this measure should be low. |
Spell engine time |
Indicates the time taken to calculate variations of the spelling and come up DYM or Autocorrect options. |
Seconds |
A low value is desired for this measure. |
Substring/Phrase time
|
Indicates the time taken for substring. |
Seconds |
|
Exact time
|
Indicates the time taken for exacting the records. |
Seconds |
Ideally, the value for this measure should be low. |
Total page render time |
Indicates the time taken to package up the page of results, including aggregation (e.g. applying rollup, paging, and relevance ranking sort). |
Seconds |
Ideally, the value for this measure should be low. |
Page render/record list time |
Indicates the total page render time minus packaging the result into a binary structure. |
Seconds |
|
Record sort initialization time |
Indicates the time taken for initialization of record sort. |
Seconds |
|
Query results sorting time |
Indicates the time taken for sorting the query results. |
Seconds |
The value for this measure should be low. A high value for this measure indicates long query processing time. |
Time taken for prefetching horizontal records |
Indicates the time taken for prefetching horizontal records. |
Seconds |
The value for this measure should be low. |
Heap sort time |
Indicates the time taken for sorting heap. |
Seconds |
The value for this measure should be low. |
Insertion sort time |
Indicates the time taken for sorting insertion. |
Seconds |
The value for this measure should be low. |
Ordinal insertion sort time |
Indicates the time taken for sorting ordinal insertion. |
Seconds |
|
Record ordinal sort time |
Indicates the time taken for sorting record ordinal. |
Seconds |
|
Radix ordinal sort time |
Indicates the time taken for sorting radix ordinal. |
Seconds |
|
Total tie-breaking sort time |
Indicates the time taken for sorting the tie-break. |
Seconds |
When two or more dimension values are assigned to the same location by the sort option or sort order then a second sort option and sort order pair can be specified to break the tie. The value for this measure should be low. |
Total identity tie-breaking sort time |
Indicates the time taken for total identity tie-breaking. |
Seconds |
|
Preprocessing time for comparison sorts |
Indicates the time taken for preprocessing comparison sorts. |
Seconds |
|
EQL stratify filter evaluation time |
Indicates the time taken for EQL stratify filter evaluation. |
Seconds |
|
Snippeting time |
Indicates the time taken to find and tag text that matched the keywords. |
Seconds |
Ideally, the value for this measure should be low. A high value indicates an increase in the query search time that can cause performance degradation in terms of latency. |