# KQL-related performance issue **URL:** \ **Category:** Kibana\ **Tags:** kql-kibana-query-language\ **Created:** [September 13, 2019, 12:06pm UTC](https://discuss.elastic.co/t/kql-related-performance-issue/199420 "2019-09-13T12:06:44Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![benpolzin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benpolzin/32/12408_2.png) [@benpolzin](https://discuss.elastic.co/u/benpolzin)\ **Post date:** [September 18, 2019, 1:18am UTC](https://discuss.elastic.co/t/kql-related-performance-issue/199420/7 "2019-09-18T01:18:04Z")
I ran this test again and I think these results from the hot nodes are only for the autocomplete suggestion queries. > I'm unsure why the actual queries aren't showing up there, unless I'm reading that wrong. I'm using filebeat's ES module to send slowlog.json to a separate monitoring ES server and used this query: `event.dataset:"elasticsearch.slowlog" and "kqlcustomer02" and host.name:(server01 or server02 or server03 or server04 or server05)` where those hostnames are the hot nodes. But then I went into my Kibana Advanced settings and set filterEditor:suggestValues to Off. And now all of my searches using KQL return lickety-split with no timeouts. I don't suppose there is a way to limit those auto-suggest queries to the time range of the actual query? Otherwise, we will live without auto-suggest. @Bargs, thank you very much for your time walking through this with me. It's greatly appreciated! --- _[View the full topic](https://discuss.elastic.co/t/kql-related-performance-issue/199420)._