Stop using SlowImpactsEnum for terms whose docFreq is less than 128.#14017
Merged
jpountz merged 1 commit intoapache:mainfrom Nov 25, 2024
Merged
Conversation
We currently use `SlowImpactsEnum` for terms whose `docFreq` is less than 128 because it's convenient as these terms don't have impacts anyway. But a recent slowdown on nightly benchmarks suggests that this contributes to making some hot calls more polymorphic than we'd like, so this PR moves such terms back to the regular impacts enums.
Contributor
Author
|
With Combined tasks in the file (call is 3-polymorphic in the baseline, bimorphic in the modified version): Without combined tasks in the file (call is bimorphic in the baseline, monomorphic in the modified version): |
jpountz
added a commit
that referenced
this pull request
Nov 25, 2024
…28. (#14017) We currently use `SlowImpactsEnum` for terms whose `docFreq` is less than 128 because it's convenient as these terms don't have impacts anyway. But a recent slowdown on nightly benchmarks suggests that this contributes to making some hot calls more polymorphic than we'd like, so this PR moves such terms back to the regular impacts enums.
benchaplin
pushed a commit
to benchaplin/lucene
that referenced
this pull request
Dec 31, 2024
…28. (apache#14017) We currently use `SlowImpactsEnum` for terms whose `docFreq` is less than 128 because it's convenient as these terms don't have impacts anyway. But a recent slowdown on nightly benchmarks suggests that this contributes to making some hot calls more polymorphic than we'd like, so this PR moves such terms back to the regular impacts enums.
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We currently use
SlowImpactsEnumfor terms whosedocFreqis less than 128 because it's convenient as these terms don't have impacts anyway. But a recent slowdown on nightly benchmarks suggests that this contributes to making some hot calls more polymorphic than we'd like, so this PR moves such terms back to the regular impacts enums.