# Just Pushed: Fine grained support for filter caching **URL:** \ **Category:** Elasticsearch\ **Created:** [October 13, 2010, 1:41am UTC](https://discuss.elastic.co/t/just-pushed-fine-grained-support-for-filter-caching/3435 "2010-10-13T01:41:22Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 13, 2010, 1:41am UTC](https://discuss.elastic.co/t/just-pushed-fine-grained-support-for-filter-caching/3435/1 "2010-10-13T01:41:22Z")
Hi, Just pushed fine grained support for filter caching: [http://github.com/elasticsearch/elasticsearch/issues/closed#issue/424](http://github.com/elasticsearch/elasticsearch/issues/closed#issue/424). The issue explains a bit what its all about, the good news is that some filters will be much faster now (ones that don't make a lot of sense to cache, like geo\_distance, as they rarely run with the same parameters). Note that when caching a filter, a price is "paid" on top of the regular filter execution at the expense of much faster execution when the same filter (with the same parameters) is used. In any case, the power is at your hands, each filter can be cacheable or not using a simple parameter in the Query DSL. For example, if geo\_distance filter is used with the same lat/lon and distance several times, it makes sense to cache. -shay.banon ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:18am UTC](https://discuss.elastic.co/t/just-pushed-fine-grained-support-for-filter-caching/3435/2 "2017-07-06T04:18:04Z")