You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2017/02/07 04:24:42 UTC
[jira] [Commented] (LUCENE-7677) Cache compound filters earlier
than regular queries
[ https://issues.apache.org/jira/browse/LUCENE-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855297#comment-15855297 ]
David Smiley commented on LUCENE-7677:
--------------------------------------
+1 nice, especially the embedded comments
> Cache compound filters earlier than regular queries
> ---------------------------------------------------
>
> Key: LUCENE-7677
> URL: https://issues.apache.org/jira/browse/LUCENE-7677
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-7677.patch
>
>
> Say you keep reusing a boolean filter that looks like "A OR B" and never use the A and B queries out of that boolean query. Currently, after this filter has been used 5 times, we would cache both A, B and "A OR B", which means that cache entries for A and B would only be built for the purpose of building a cache entry for "A OR B", which is wasteful.
> By caching compound queries a bit earlier, we could make it less likely to happen since:
> - we only consider queries as consumed if a scorer is pulled
> - once the boolean query is cached, we stop pulling scorers on the A and B queries
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org