You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Ignacio Vera (Jira)" <ji...@apache.org> on 2020/03/24 14:33:00 UTC
[jira] [Resolved] (LUCENE-9287) Never cache
DocValuesFieldExistsQuery
[ https://issues.apache.org/jira/browse/LUCENE-9287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ignacio Vera resolved LUCENE-9287.
----------------------------------
Fix Version/s: 8.6
Assignee: Ignacio Vera
Resolution: Fixed
> Never cache DocValuesFieldExistsQuery
> -------------------------------------
>
> Key: LUCENE-9287
> URL: https://issues.apache.org/jira/browse/LUCENE-9287
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Ignacio Vera
> Assignee: Ignacio Vera
> Priority: Minor
> Fix For: 8.6
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org