# 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:** 14

<div class="post-metadata">

**Author:** ![itizir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itizir/32/63552_2.png) [@itizir](https://discuss.elastic.co/u/itizir)\
**Post date:** [March 23, 2020, 5:26pm UTC](https://discuss.elastic.co/t/time-range-query-performance-7-6/223194/14 "2020-03-23T17:26:20Z")

</div>

Oooh, this is very interesting! Thanks!

So basically `exists` is so slow because it spends time caching _all_ the documents (since they all have the timestamp field)? Still annoying, but at least it makes sense now.

Is there any way to disable the caching of specific terms of parts of queries, or something like this?

---

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