|
@@ -411,6 +411,7 @@ Some caveats to the Profile API are that:
|
|
|
- given the added overhead, the resulting took times are not reliable indicators of actual took time, but can be used comparatively between clauses for relative timing differences
|
|
|
- the Profile API is best for exploring possible reasons behind the most costly clauses of a query but isn't intended for accurately measuring absolute timings of each clause
|
|
|
|
|
|
+[[faster-phrase-queries]]
|
|
|
=== Faster phrase queries with `index_phrases`
|
|
|
|
|
|
The <<text,`text`>> field has an <<index-phrases,`index_phrases`>> option that
|
|
@@ -418,6 +419,7 @@ indexes 2-shingles and is automatically leveraged by query parsers to run phrase
|
|
|
queries that don't have a slop. If your use-case involves running lots of phrase
|
|
|
queries, this can speed up queries significantly.
|
|
|
|
|
|
+[[faster-prefix-queries]]
|
|
|
=== Faster prefix queries with `index_prefixes`
|
|
|
|
|
|
The <<text,`text`>> field has an <<index-phrases,`index_prefixes`>> option that
|