[LUCENE-8922] Speed up retrieval of top hits of DisjunctionMaxQuery

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 8.3
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Adrien Grand
• Created: 17/Jul/19 08:33
• Updated: 28/Aug/22 15:49
• Resolved: 25/Jul/19 18:12

Description

There a simple optimization that we are not doing in the case that tieBreakMultiplier is 0: we could propagate the min competitive score to sub clauses as-is.

Even in the general case, we currently compute the block boundary of the DisjunctionMaxQuery as the minimum of the block boundaries of its sub clauses. This generates blocks that have very low score upper bounds but unfortunately they are also very small, which means that we might sometimes not make progress quickly enough.

Issue Links

• links to: GitHub Pull Request #791