[LUCENE-8213] Cache costly subqueries asynchronously

• Type: Improvement
• Status: Reopened
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 7.2.1
• Component/s: core/query/scoring
• Labels: performance
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Amir Hadadi
• Created: 17/Mar/18 16:43
• Updated: 28/Aug/22 15:26

Description

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.

Issue Links

• is related to: LUCENE-9002 query caching leads to absurdly slow queries
• links to: GitHub Pull Request #815
• links to: GitHub Pull Request #914
• links to: GitHub Pull Request #916
• links to: GitHub Pull Request #1044