These statistics are only available when the
--showProfiles flag is enabled.
========================================================================= == Request Profiling ========================================================================= ----- Number of Base Records Requested ----- Requests Analyzed: 169 Average: 14.734 Standard Deviation: 1.119 Maximum: 15 Minimum: 10 Over Threshold (50): 0 (0.000%) ----- Number of Aggregate Records Requested ----- Requests Analyzed: 666 Average: 14.932 Standard Deviation: 1.004 Maximum: 15 Minimum: 0 Over Threshold (50): 0 (0.000%)
This section displays metrics for the individual feature configuration specified for each request processed by the MDEX Engine. Because request profiling requires deeper analysis of request URLs, enabling profiling slows down the Request Log Analyzer's processing.
The output in this section does not include Web Service queries. Because of this, the percentages may add up to less than 100%. (For example, if 80% of all queries are Web Service queries, then the total of all percentages in this section will add up to 20%.)
The following metrics are output within this section:
Number of Base Records Requested: for base navigation or search queries, the number of base records that the Presentation API specified should be returned in detail. The MDEX Engine response includes the full content of a certain number of records (the "current page" of records) as well as available navigation and other meta information about the remaining records. This metric measures the number of records included in the current page; the more records, the larger the resulting data packet.
Number of Aggregate Records Requested: for aggregate navigation or search queries, the number of aggregate records that the Presentation API specified should be returned in detail. The MDEX Engine response includes the full content of a certain number of records (the "current page" of records) as well as available navigation and other meta information about the remaining records. This metric measures the number of records included in the current page; the more records, the larger the resulting data packet.
Pagination Offset: for navigation or search queries, the pagination offset specified by the query. When paginating through result sets, the pagination offset sets which page of results should be the current page. Higher pagination offsets are more expensive for the MDEX Engine to compute.
Number of Navigation Descriptors (not including N=0): for navigation or search queries, this metric measures the number of navigation nodes specified as descriptors by the query. This metric ignores queries that only specify the root node (N=0).
Number of Exposed Dimensions (not including none or allgroups): for navigation or search queries, this metric measures the number of refinement dimensions opened by the query. This metric ignores queries that open no dimensions and queries that open all dimensions.
Number of Explicit Sort Keys: for navigation or search queries, this metric measures the number of record sort orders specified for the query. This metric ignores queries do not specify a sort order, such as those queries that sort by search relevance or by the default sort order specified in dgidx.
Number of Search Terms: for search queries, this metric measures the number of search terms specified in the query. The number of terms is calculated by splitting the entire search string on whitespace. This is an approximation; the MDEX Engine can also split terms on punctuation characters.
Number of Search Keys: for search queries, this metric measures the number of search keys (interfaces) specified in the query. If the same key is specified twice, it counts as two keys.
