honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-22 21:05:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix to edit in recent cherry-pick

Browse Source
This commit is contained in:
Peter Dyson 2019-01-04 17:26:42 +10:00 committed by GitHub
parent 3578e69669
commit 7cc9754d94
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/reference/how-to/search-speed.asciidoc
View File

@ -413,6 +413,7 @@ of the node containing each copy of the shard. This can improve query throughput
and reduce latency for search-heavy applications.
=== Tune your queries with the Profile API
:ref: https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html
:ref-searchprofiler: https://www.elastic.co/guide/en/kibana/current/xpack-profiler.html
@ -425,4 +426,4 @@ Some caveats to the Profile API are that:
- the Profile API as a debugging tool adds significant overhead to search execution and can also have a very verbose output
- 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
>>>>>>> 13f5c884260... Add Profile API to search speed tuning howto (#29489)