Last Updated : May 2020
After you finish reading these quick tips we recommend you run our Elasticsearch Check-Up – get personalized recommendations that can sustainably improve your search performance (no installation required)!
Here are 10 tips on how to reduce Elasticsearch search latency and optimize search performance:
- Size Parameter
Assigning a huge value to size parameter causes Elasticsearch to compute vast amounts of hits, which causes severe performance issues. Instead of setting a huge size, you should batch requests in small sizes.
- Shards and Replicas
Optimize necessary index settings that play a crucial role in Elasticsearch performance, like the number of shards and replicas. In many cases having more replicas helps improve search performance. Please refer to Opster’s guide on shards and replicas to learn more.
- Deleted Documents
Having a large number of deleted documents in the Elasticsearch index also causes search performance issues, as explained in this official document. Force merge API can be used to remove a large number of deleted documents and optimize the shards.
- Search Filters
Effective use of filters in Elasticsearch queries can improve search performance dramatically as the filter clauses are 1) cached, and 2) able to reduce the target documents to be searched in the query clause.
- Wildcard Queries
Avoid wildcard, especially leading wildcard queries, which causes the entire Elasticsearch index to be scanned.
- Regex and Parent-Child
Note that Regex queries and parent-child can cause search latency.
- Implementing Features
There are multiple ways to implement a specific feature in Elasticsearch. For example, Autocomplete can be implemented in various styles. Opster’s blog gives a 360-degree view of both functional and non-functional features (especially performance).
- Multitude of Small Shards
Having many small shards could cause a lot of network calls and threads, which severely impact search performance; please refer to this real-world case study by Opster’s expert on this topic.
- Heavy Aggregations
Avoid heavy aggregations that involve unique IDs. Refer to Opster’s slow logs guide to identify such search slow logs effectively.
- Timeout and Terminate
Timeout param and terminate after param can be useful when executing heavy searches, or when result data is vast. This official guide can help.