[
https://issues.apache.org/jira/browse/LUCENE-9857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314879#comment-17314879
]
Feng Guo commented on LUCENE-9857:
----------------------------------
Thank you for the reply! I'm so sorry that i did not notice this code you point
out. I'm digging into a case that queries become slower after a forcemerge, but
obviously this issue is not the root cause now. Thank you again for the
explaination!
> Skip cache building if IndexOrDocValuesQuery choose the dvQuery
> ---------------------------------------------------------------
>
> Key: LUCENE-9857
> URL: https://issues.apache.org/jira/browse/LUCENE-9857
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: main (9.0)
> Reporter: Feng Guo
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IndexOrDocValuesQuery can automatically use dvQueries when the cost > 8 *l
> eadcost, And the LRUQueryCache skips cache building when cost > 250(By
> default) * leadcost. There is a gap between 8 and 250, which means if the
> factor is just between 8 and 250 (e.g. cost = 10 * leadcost), the
> IndexOrDocValueQuery will choose the dvQueries but LRUQueryCache still build
> cache for it.
> IndexOrDocValuesQuery aims to speed up queries when the leadcost is small,
> but building cache by dvScorers can make it meaningless because it needs to
> scan all the docvalues. This can be rather slow for big segments, so maybe we
> should skip the cache building for IndexOrDocValuesQuery when it chooses
> dvQueries.
--
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
