Wraps all iterator with likelyImpactsEnum under BlockMaxConjunctionBulkScorer #15004
+7
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Like #14023, this PR propose to wrap all iterators (not just the lead) with
ScorerUtil::likelyImpactsEnum
, it seems to be helpful withScorerUtil.applyRequiredClause
(I guess).As before, I ran luceneutil on
wikimediumall
withsearchConcurrency=0, taskCountPerCat=5, taskRepeatCount=50
, result after 20 iterations are shown below:What I'm curious about is that many
Or
type tasks clustered at the top, which might not be coincident ?