Add MaxScale config parameter to ExponentialHistogram #5044
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.
Implements spec opentelemetry-specification#3017.
As stated in opentelemetry-specification#2987), this would allow performance sensitive applications to reduce the number of rescales and avoid the performance hit of computing histogram bucket using the log approach required for positive scales, which is slower than bitshifting approach used when scale is <= 0. I suspect only the most extreme applications would care to set this since its pretty extreme to care about a single call to
Math.log
being on the hot path.