These statistics are only available when the
--showExtendedTypes flag is enabled.
========================================================================= == Extended Query Types ========================================================================= ----- Did-You-Mean Enabled Searches ----- Number of Requests: 663 (50.189%) Avg Response Time (ms): 107.990 Avg Engine Time (ms): 58.926 Avg Response Size (bytes): 28302.454 Request Times over 1250 ms: 1 (0.151%) Engine Times over 750 ms: 2 (0.302%) ----- Searches Including Wildcards ----- Number of Requests: 0 (0.000%)
This section displays statistics categorized by the features enabled on each query processed by the MDEX Engine. (The output in this section does not include Web Service queries.) The sum of the percentages of each extended query type can be more or less than 100%, since any one query can enable none, one, or more than one of these features. The total may also be less than 100% because the percentages do not include Web Service queries. (For example, if most of the Dgraph queries are Web Service queries, then the totals in this section will likely add up to much less than 100%.)
The following extended query types are output within this section:
Did-You-Mean Enabled Searches: search queries that enable the "Did you mean?" feature, typically using the
Nty=1URL parameter or thesetNavERecSearchDidYouMean()API method.Searches Including Wildcards: search queries that include a wildcard character (*) within the search terms. Note that the inclusion of a wildcard character does not necessarily mean that the MDEX Engine performed a wildcard search, since it is not necessarily true that the target search interface was enabled for wildcarding. Wildcard searches are more expensive than standard searches.
Boolean Searches: search queries that specified the matchboolean matchmode, typically using the
NtxURL parameter or by specifying the mode within theERecSearchobject's constructor in the Presentation API. Boolean searches can be more expensive than standard searches.Requests Including a Record Filter: navigation, search, dimension search, or aggregate record queries that specify a record filter, typically using the
NrURL parameter or thesetNavRecordFilter()API method.Requests Including a Range Filter: navigation, search, dimension search, or aggregate record queries that specify a range filter, typically using the
NfURL parameter or thesetNavRangeFilters()API method. This category does not include geocode filters, even though geocode filters use the same URL parameters and API methods.Requests Including a Geocode Filter: navigation, search, dimension search, or aggregate record queries that specify a geocode filter, typically using the
NfURL parameter or thesetNavRangeFilters()API method. This category does not include other range filters, even though other range filters use the same URL parameters and API methods.Aggregate requests: navigation or search requests that specify an aggregate record rollup key, typically using the
NuURL parameter or thesetNavRollupKey()API method.Base requests: navigation or search requests that do not specify an aggregate record rollup key.
Requests Exposing All Refinements (allgroups): navigation or search requests that open all available dimension refinements by using the
setNavAllRefinements(true)API method (there is no corresponding URL parameter). This can be an expensive configuration because it increases both MDEX Engine calculation requirements and response packet size.Requests with an Explicit Sort Order: navigation or search requests that specify one or more keys by which to sort results, typically using the
NsURL parameter or thesetNavActiveSortKeys()API method. This does not include requests that use the default sort order specified in Dgidx, nor does it include search requests that are sorted by relevancy (the default for searches).Multi-Key Search Requests: search requests that specify more than one search key, even if the multiple searches utilize the same interface, typically by pipe-delimiting the
NttandNtkURL parameters or by specifying more than oneERecSearchin anERecSearchListwithin the API. Multi-key searches are typically generated by search-within functionality or on advanced search pages that include parametric search functionality.
