[LUCENE-8027] Do not cache clauses if they might make the query more than X times slower

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Adrien Grand
• Created: 31/Oct/17 10:24
• Updated: 28/Aug/22 15:21

Description

Query caching can have a negative impact on tail latencies as the clause that is cached needs to be entirely consumed. Maybe we could leverage the fact that we can know the lead cost from any scorer now (LUCENE-7897) in order to implement heuristics that would look like "do not cache clause X if its cost is 10x greater than the cost of the entire query". This would make sure that a fast query can not become absurdly slow just because it had to cache a costly filter. The filter will need to wait for a more costly query to be cached, or might never be cached at all.

Issue Links

• is related to: LUCENE-9002 query caching leads to absurdly slow queries