# Time range query performance \[7.6\]

**URL:** <https://discuss.elastic.co/t/time-range-query-performance-7-6/223194>\
**Category:** Elasticsearch\
**Created:** [March 11, 2020, 6:43pm UTC](https://discuss.elastic.co/t/time-range-query-performance-7-6/223194 "2020-03-11T18:43:54Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![Ignacio\_Vera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ignacio_vera/32/36674_2.png) [@Ignacio\_Vera](https://discuss.elastic.co/u/Ignacio_Vera)\
**Post date:** [March 24, 2020, 2:49pm UTC](https://discuss.elastic.co/t/time-range-query-performance-7-6/223194/15 "2020-03-24T14:49:44Z")

</div>

I am afraid you cannot disable parts on the query cache.

On the other hand, I have discussed this behaviour with other people and we agreed that we should not cache `DocValuesFieldExistsQuery` as the query is already very fast and the overhead makes little sense. This has been already fixed in the upstream project: [https://issues.apache.org/jira/browse/LUCENE-9287](https://issues.apache.org/jira/browse/LUCENE-9287)

---

_[View the full topic](https://discuss.elastic.co/t/time-range-query-performance-7-6/223194)._