[
https://issues.apache.org/jira/browse/LUCENE-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984472#comment-16984472
]
ASF subversion and git services commented on LUCENE-8213:
---------------------------------------------------------
Commit 09cd82a6fc51b90275ed326812e1d947c863952e in lucene-solr's branch
refs/heads/revert-916-revised_LUCENE-8213 from Atri Sharma
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=09cd82a ]
Revert "LUCENE-8213: Asynchronous Caching in LRUQueryCache (#916)"
This reverts commit 2d98a619dd96abfa716098bbc5cac2bc3a1b7d49.
> Cache costly subqueries asynchronously
> --------------------------------------
>
> Key: LUCENE-8213
> URL: https://issues.apache.org/jira/browse/LUCENE-8213
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/query/scoring
> Affects Versions: 7.2.1
> Reporter: Amir Hadadi
> Priority: Minor
> Labels: performance
> Attachments:
> 0001-Reproduce-across-segment-caching-of-same-query.patch,
> thetaphi_Lucene-Solr-master-Linux_24839.log.txt
>
> Time Spent: 21h 10m
> Remaining Estimate: 0h
>
> IndexOrDocValuesQuery allows to combine costly range queries with a selective
> lead iterator in an optimized way. However, the range query at some point
> gets cached by a querying thread in LRUQueryCache, which negates the
> optimization of IndexOrDocValuesQuery for that specific query.
> It would be nice to see an asynchronous caching implementation in such cases,
> so that queries involving IndexOrDocValuesQuery would have consistent
> performance characteristics.
--
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
