# Enabling filter cache **URL:** \ **Category:** Elasticsearch\ **Created:** [April 22, 2015, 6:41pm UTC](https://discuss.elastic.co/t/enabling-filter-cache/23366 "2015-04-22T18:41:55Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Ed\_Kim](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@Ed\_Kim](https://discuss.elastic.co/u/Ed_Kim)\ **Post date:** [April 22, 2015, 6:41pm UTC](https://discuss.elastic.co/t/enabling-filter-cache/23366/1 "2015-04-22T18:41:55Z")
Hi, I have a dynamic query built via java api that assembles a filtered query depending on the parameter input. I have about a dozen filters (mostly term filters) that may or may not be used, and had a couple questions: 1. Is it ok to simply set the parent boolFilterBuilder cache setting to true, or do I need to set cache=true for each filter? 2. Would it be a good practice to execute a dummy query with all the filters to preemptively create the filter before it's released for actual use? Thanks in advance for your time -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/af0fc6a1-4951-4c83-9642-cb6b12e3e56f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/af0fc6a1-4951-4c83-9642-cb6b12e3e56f%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [April 22, 2015, 6:53pm UTC](https://discuss.elastic.co/t/enabling-filter-cache/23366/2 "2015-04-22T18:53:06Z")
On Wed, Apr 22, 2015 at 2:41 PM, Ed Kim [edkim81@gmail.com](mailto:edkim81@gmail.com) wrote: > Hi, I have a dynamic query built via java api that assembles a filtered > query depending on the parameter input. I have about a dozen filters > (mostly term filters) that may or may not be used, and had a couple > questions: > > 1. Is it ok to simply set the parent boolFilterBuilder cache setting to > true, or do I need to set cache=true for each filter? Those do different things. One caches the combined results and one caches each term. To be honest term filter are rarely worth caching because just hitting lucene for them is so fast. 1. Would it be a good practice to execute a dummy query with all the > filters to preemptively create the filter before it's released for actual > use? This is what warmers are for. They are applied to new segments to eagerly load stuff including the filter cache. Elasticsearch's filer cache is per segment so this is a good match. Its also why the filter cache doesn't have to be invalidated - segments are write only and deletes are applied after the results from the filter cache. Nik -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Ed\_Kim](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@Ed\_Kim](https://discuss.elastic.co/u/Ed_Kim)\ **Post date:** [April 22, 2015, 6:58pm UTC](https://discuss.elastic.co/t/enabling-filter-cache/23366/3 "2015-04-22T18:58:26Z")
In terms of performance, we we talking nanoseconds saved by using term filters, or possibly a few milliseconds? Given the performance requirements for this query, even saving a few milliseconds is a lot. Also, it looks like I should cache at the individual filter level, as they will be bundled differently depending on the params. Thanks for the clarification! On Wed, Apr 22, 2015 at 11:53 AM, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > On Wed, Apr 22, 2015 at 2:41 PM, Ed Kim [edkim81@gmail.com](mailto:edkim81@gmail.com) wrote: > > > Hi, I have a dynamic query built via java api that assembles a filtered > > query depending on the parameter input. I have about a dozen filters > > (mostly term filters) that may or may not be used, and had a couple > > questions: > > > > 1. Is it ok to simply set the parent boolFilterBuilder cache setting to > > true, or do I need to set cache=true for each filter? > > Those do different things. One caches the combined results and one caches > each term. To be honest term filter are rarely worth caching because just > hitting lucene for them is so fast. > > 1. Would it be a good practice to execute a dummy query with all the > > > filters to preemptively create the filter before it's released for actual > > use? > > This is what warmers are for. They are applied to new segments to eagerly > load stuff including the filter cache. Elasticsearch's filer cache is per > segment so this is a good match. Its also why the filter cache doesn't have > to be invalidated - segments are write only and deletes are applied after > the results from the filter cache. > > Nik > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/nVQyRc-AKDM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/nVQyRc-AKDM/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [April 22, 2015, 7:37pm UTC](https://discuss.elastic.co/t/enabling-filter-cache/23366/4 "2015-04-22T19:37:31Z")
With term queries I imagine its nanoseconds to a net loss to use the filter cache. You should really test it though because I'm not 100% sure. There was talk of elassticsearch being more intelligent about which filters it decides to cache but I don't know where that's gone. Nik On Wed, Apr 22, 2015 at 2:58 PM, Eddie Kim [edkim81@gmail.com](mailto:edkim81@gmail.com) wrote: > In terms of performance, we we talking nanoseconds saved by using term > filters, or possibly a few milliseconds? Given the performance requirements > for this query, even saving a few milliseconds is a lot. Also, it looks > like I should cache at the individual filter level, as they will be bundled > differently depending on the params. Thanks for the clarification! > > On Wed, Apr 22, 2015 at 11:53 AM, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) > wrote: > > > On Wed, Apr 22, 2015 at 2:41 PM, Ed Kim [edkim81@gmail.com](mailto:edkim81@gmail.com) wrote: > > > > > Hi, I have a dynamic query built via java api that assembles a filtered > > > query depending on the parameter input. I have about a dozen filters > > > (mostly term filters) that may or may not be used, and had a couple > > > questions: > > > > > > 1. Is it ok to simply set the parent boolFilterBuilder cache setting to > > > true, or do I need to set cache=true for each filter? > > > > Those do different things. One caches the combined results and one caches > > each term. To be honest term filter are rarely worth caching because just > > hitting lucene for them is so fast. > > > > 1. Would it be a good practice to execute a dummy query with all the > > > > > filters to preemptively create the filter before it's released for actual > > > use? > > > > This is what warmers are for. They are applied to new segments to eagerly > > load stuff including the filter cache. Elasticsearch's filer cache is per > > segment so this is a good match. Its also why the filter cache doesn't have > > to be invalidated - segments are write only and deletes are applied after > > the results from the filter cache. > > > > Nik > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/nVQyRc-AKDM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/nVQyRc-AKDM/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0u3aX\_oOu2v\_0WcPAygDPWba%3DCBhe-\_oRinS8BjEQpkQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0u3aX_oOu2v_0WcPAygDPWba%3DCBhe-_oRinS8BjEQpkQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Ed\_Kim](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@Ed\_Kim](https://discuss.elastic.co/u/Ed_Kim)\ **Post date:** [April 22, 2015, 10:15pm UTC](https://discuss.elastic.co/t/enabling-filter-cache/23366/5 "2015-04-22T22:15:00Z")
I'm a bit confused, is terms filter slower because it has to iterate through a list of bitsets whereas lucene already has access to the list of matching documents via inverted index? Also, if I set cache=true for each individual filter, does it allow me to create any permutation of my bool filter (given a set of filters) and make use of the cache? Or will this create a new filter cache? On Wed, Apr 22, 2015 at 12:37 PM, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > With term queries I imagine its nanoseconds to a net loss to use the > filter cache. You should really test it though because I'm not 100% sure. > > There was talk of elassticsearch being more intelligent about which > filters it decides to cache but I don't know where that's gone. > > Nik > > On Wed, Apr 22, 2015 at 2:58 PM, Eddie Kim [edkim81@gmail.com](mailto:edkim81@gmail.com) wrote: > > > In terms of performance, we we talking nanoseconds saved by using term > > filters, or possibly a few milliseconds? Given the performance requirements > > for this query, even saving a few milliseconds is a lot. Also, it looks > > like I should cache at the individual filter level, as they will be bundled > > differently depending on the params. Thanks for the clarification! > > > > On Wed, Apr 22, 2015 at 11:53 AM, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) > > wrote: > > > > > On Wed, Apr 22, 2015 at 2:41 PM, Ed Kim [edkim81@gmail.com](mailto:edkim81@gmail.com) wrote: > > > > > > > Hi, I have a dynamic query built via java api that assembles a filtered > > > > query depending on the parameter input. I have about a dozen filters > > > > (mostly term filters) that may or may not be used, and had a couple > > > > questions: > > > > > > > > 1. Is it ok to simply set the parent boolFilterBuilder cache setting to > > > > true, or do I need to set cache=true for each filter? > > > > > > Those do different things. One caches the combined results and one > > > caches each term. To be honest term filter are rarely worth caching because > > > just hitting lucene for them is so fast. > > > > > > 1. Would it be a good practice to execute a dummy query with all the > > > > > > > filters to preemptively create the filter before it's released for actual > > > > use? > > > > > > This is what warmers are for. They are applied to new segments to > > > eagerly load stuff including the filter cache. Elasticsearch's filer cache > > > is per segment so this is a good match. Its also why the filter cache > > > doesn't have to be invalidated - segments are write only and deletes are > > > applied after the results from the filter cache. > > > > > > Nik > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/nVQyRc-AKDM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/nVQyRc-AKDM/unsubscribe). > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com) > > > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0VNMNL3MZQ%2BAHn5EH4N%3DQRpqjS9UqQMEZ-yY82C4-ozA%40mail.gmail.com?utm_medium=email&utm_source=footer) > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAPh7Qf%3D%2BwhtG%3D21SRVeE-XdEbMXoHK1%3D8tKikp2ken8uza4z6g%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/nVQyRc-AKDM/unsubscribe](https://groups.google.com/d/topic/elasticsearch/nVQyRc-AKDM/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0u3aX\_oOu2v\_0WcPAygDPWba%3DCBhe-\_oRinS8BjEQpkQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0u3aX_oOu2v_0WcPAygDPWba%3DCBhe-_oRinS8BjEQpkQ%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0u3aX\_oOu2v\_0WcPAygDPWba%3DCBhe-\_oRinS8BjEQpkQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0u3aX_oOu2v_0WcPAygDPWba%3DCBhe-_oRinS8BjEQpkQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPh7Qfn6wAv069-OR09nSQr1UZ9r5ofGXHGg1cguzDNfXkFLTA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPh7Qfn6wAv069-OR09nSQr1UZ9r5ofGXHGg1cguzDNfXkFLTA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:18am UTC](https://discuss.elastic.co/t/enabling-filter-cache/23366/6 "2017-07-06T00:18:10Z")