# Will the filter cache become a bad thing in some situation?

**URL:** <https://discuss.elastic.co/t/will-the-filter-cache-become-a-bad-thing-in-some-situation/44677>\
**Category:** Elasticsearch\
**Created:** [March 17, 2016, 8:53am UTC](https://discuss.elastic.co/t/will-the-filter-cache-become-a-bad-thing-in-some-situation/44677 "2016-03-17T08:53:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kramer\_Li](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kramer_li/32/46872_2.png) [@Kramer\_Li](https://discuss.elastic.co/u/Kramer_Li)\
**Post date:** [March 17, 2016, 8:53am UTC](https://discuss.elastic.co/t/will-the-filter-cache-become-a-bad-thing-in-some-situation/44677/1 "2016-03-17T08:53:58Z")

</div>

For example, if you have one thousand query. There are 1000 filter which keep in memory and being updated periodically.

Will it be a big cost?

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [March 18, 2016, 3:21pm UTC](https://discuss.elastic.co/t/will-the-filter-cache-become-a-bad-thing-in-some-situation/44677/2 "2016-03-18T15:21:11Z")

</div>

For the most part keeping the filter cache doesn't come up as an issue. I've seen issues where people want more control over what gets cached on this forum, but not seen issues with overhead.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:07pm UTC](https://discuss.elastic.co/t/will-the-filter-cache-become-a-bad-thing-in-some-situation/44677/3 "2017-07-05T23:07:10Z")

</div>