You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2016/02/26 18:21:18 UTC
[jira] [Commented] (LUCENE-7050) Improve the query cache heuristic
to detect costly queries
[ https://issues.apache.org/jira/browse/LUCENE-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169355#comment-15169355 ]
Robert Muir commented on LUCENE-7050:
-------------------------------------
On the idea of a method or interface, are we sure caching is the only use case? What about eg reordering clauses for more efficiency and other potential uses?
Im not opposed to the hacky solution since its just a default impl... But if we can come up with a very nice name... Then i think it would be cleaner for queries to confess that processing just a few docs is just as costly as processing all docs.
> Improve the query cache heuristic to detect costly queries
> ----------------------------------------------------------
>
> Key: LUCENE-7050
> URL: https://issues.apache.org/jira/browse/LUCENE-7050
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-7050.patch
>
>
> Term queries, phrase queries and their combinations through boolean queries should not be cached too agressively since they can efficiently make use of skip lists. However we also have a number of queries that in practice need to visit all matches anyway like PrefixQuery, TermsQuery, PointInSetQuery, PointRangeQuery, so caching them more agressively can help avoid computing all documents that match in the whole index again and again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org