[
https://issues.apache.org/jira/browse/LUCENE-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17439096#comment-17439096
]
Adrien Grand commented on LUCENE-10120:
---------------------------------------
Thanks [~ChrisLu], I understand this but wonder about the queries that end up
matching contiguous ranges of doc IDs. This is not typical, so I'm assuming
that there is something special about how the index is build (e.g. index
sorting) or the query that makes it likely to match a contiguous range of doc
IDs.
Can you share the queries that would use this optimization in your case?
> Lazy initialize FixedBitSet in LRUQueryCache
> --------------------------------------------
>
> Key: LUCENE-10120
> URL: https://issues.apache.org/jira/browse/LUCENE-10120
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: main (10.0)
> Reporter: Lu Xugang
> Priority: Major
> Attachments: 1.png, LUCENE-10120.patch
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Basing on the implement of collecting docIds in DocsWithFieldSet, may be we
> could do similar way to cache docIdSet in
> *LRUQueryCache#cacheIntoBitSet(BulkScorer scorer, int maxDoc)* when docIdSet
> is density.
> In this way , we do not always init a huge FixedBitSet which sometime is not
> necessary when maxDoc is large
>
>
>
--
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
