[ 
https://issues.apache.org/jira/browse/SOLR-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267860#comment-16267860
 ] 

Shawn Heisey commented on SOLR-11684:
-------------------------------------

bq. LUCENE-7680 adds rules like a term query is always cheap . So don't cache it

I'm really not familiar with how likely it is that something a user passes in 
the fq parameter will ultimately result in a term query, as opposed to some 
other kind of query.  If that's what happens, then it sounds like we can choose 
to NOT cache the filter.

I really have no idea what Solr actually does at the Lucene layer, but I do 
know that some of the filters my servers receive can take double-digit seconds 
to run, at least until the filter ends up in the cache, at which point it 
becomes REALLY fast.


> Solr should not cache cheap filters
> -----------------------------------
>
>                 Key: SOLR-11684
>                 URL: https://issues.apache.org/jira/browse/SOLR-11684
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Varun Thacker
>
> In the past I've seen clients who disabled the filter cache saw better query 
> performance. 
> I've never got the chance to investigate this unfortuinately. 
> I was reading through 
> https://lucidworks.com/2017/11/27/caching-and-filters-and-post-filters/ today 
> and this section is something I wanted to revisit
> {code}
> cache=false – Tells Solr that we don't need/want this filter to be cached 
> independently for re-use.
>  This will allow Solr to evaluate these filters at the same time it's 
> processing the main query
> {code}
> Lucene does optimizations like LUCENE-7680 (I think there are more which I 
> can link later on). Maybe Solr should also consult 
> UsageTrackingQueryCachingPolicy and not cache certain cheap filters?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to