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
This PR propose to introduce a new
forEachapi onImpacts. It seems to be helpful to reduce the cost ofMaxScoreCache.computeMaxScore. I've tried many other ways, to avoid adding a new api but failed to get the same performance gain. like explictly implementMutableImpactList.forEach(also included in this PR for now).Actually I'm not very sure about the root cause of the performance gain, especilly when the explict
forEachforMutableImpactListdidn't work out wellThis PR is still a draft, includes many duplicate code, tests are not added, nor is the java doc. I'm not sure whether this change is desired, any comments and suggestions are welcome !!
Here is the luceneutil benchmark result on
wikimediumallwithsearchConcurrency=0, taskCountPerCat=5, taskRepeatCount=50after 20 iterations: