# Query\_string performance

**URL:** <https://discuss.elastic.co/t/query-string-performance/86808>\
**Category:** Kibana\
**Created:** [May 23, 2017, 12:45pm UTC](https://discuss.elastic.co/t/query-string-performance/86808 "2017-05-23T12:45:46Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![baltendo](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@baltendo](https://discuss.elastic.co/u/baltendo)\
**Post date:** [May 23, 2017, 1:46pm UTC](https://discuss.elastic.co/t/query-string-performance/86808/3 "2017-05-23T13:46:03Z")

</div>

I added also a thread in Elasticsearch:

> [@Query\_string performance issue](https://discuss.elastic.co/t/query-string-performance-issue/86818):
>
> Hi! Initially I posted this issue in Kibana but I was asked to post it here as well: Kibana: [Query\_string performance](https://discuss.elastic.co/t/query-string-performance/86808) We recently upgraded Elasticsearch and Kibana from 5.3.0 to 5.4.0 and since then we experience performance issues with dashboards and visualizations. Here is the query that is generated by Kibana for a visualization on the .monitoring-es-2-\* index: { "query": { "bool": { "must": [ { "query\_string": { "analyze\_wildcard": true, …

But the problem with the duplicated `query_string` blocks is on Kibana side I guess?

BTW: We just found a workaround to improve the performance by disabling the `_all` field and using the `index.query.default_field` which prevents Elasticsearch from looking into every "queryable" field.

---

_[View the full topic](https://discuss.elastic.co/t/query-string-performance/86808)._