[
https://issues.apache.org/jira/browse/LUCENE-9287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17065831#comment-17065831
]
ASF subversion and git services commented on LUCENE-9287:
---------------------------------------------------------
Commit 955c67d066f766f16f41bc828a1fca6275387b63 in lucene-solr's branch
refs/heads/branch_8x from Ignacio Vera
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=955c67d ]
LUCENE-9287: UsageTrackingQueryCachingPolicy no longer caches
DocValuesFieldExistsQuery (#1374)
> Never cache DocValuesFieldExistsQuery
> -------------------------------------
>
> Key: LUCENE-9287
> URL: https://issues.apache.org/jira/browse/LUCENE-9287
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Ignacio Vera
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently {{DocValuesFieldExistsQuery}} is cached if there are no DV updates
> on the field in question. This query is pretty efficient and some experiments
> show that caching the result might be much more expensive than the benefits
> we get from caching the result.
> For example, indexing 10 million documents with long values and then
> executing this query:
> * without caching it takes around 1ms to run.
> * with caching it takes around 40ms to run and the size of the cache is
> around 1MB (1212792 bytes).
> I wonder if we should never cache this query as it seems the overhead of
> caching the results is not worthy.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
