The following metrics are found in multiple sections of the Request Log Analyzer output:
Ops/Sec: operations per second; the number of requests processed in a time period, divided by the number of seconds in that time period. This metric provides a sense of achieved throughput. In other words, this metric shows how well the MDEX Engine is servicing simultaneous clients. Note that this is achieved performance, not potential performance; see Result Interpretation.
Round-Trip Response Time or Response Time: the total time required for the Endeca API to receive a response back from an MDEX Engine. This includes time spent in the request queue, time spent processing in the engine, and time spent writing the response back to the API. The round-trip response time is the time seen by end users of the system.
Response Times Over [threshold]: the number of requests that took longer than [threshold] to complete, measured by round-trip response time. The [threshold] value is configurable with the
--threshResponseflag. Typically, this metric is followed by the percentage of over-threshold requests compared to all requests.Engine-Only Processing Time or Engine Time: the total time required for the Endeca MDEX Engine to calculate the results of a query. This includes only the time spent processing in the engine, excluding time spent in the request queue and time spent writing the response back to the API. The engine-only processing time is a measure of the expensiveness of any particular query.
Engine Times Over [threshold]: the number of requests that took longer than [threshold] to complete, measured by engine-only processing time. The [threshold] value is configurable with the
--threshEngineflag. Typically, this metric is followed by the percentage of over-threshold requests compared to all requests.Response Size: the size of the data packet returned by the MDEX Engine to the API. As data packet sizes grow larger, more network resources are required to move the data. Additionally, larger data packets typically require more computing resources in the MDEX Engine and the Endeca API to pack and unpack the data.
Number of Requests: when categorizing metrics by type, such as when using
--showResponseCodesto display 404 Not Found responses, Number of Requests denotes the total quantity of requests in the category. This metric is typically followed by the percentage of these requests compared to all requests.Requests Analyzed: when calculating individual metrics, such as when using
--showProfilesto display the number of base records requested, Requests Analyzed denotes the number of requests polled to calculate the metric.
