Fix huge allocation overhead in UnstableRateCounter
#26976
Merged
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.
Overview
Currently
UnstableRateCounter
is allocationg a new array of size of judged objects on each judgement, which quickly becoming a problem for maps with many objects. By using Welford's online algorithm we can avoid selection and multiple passes over hitEvents and compute UR in a single loop.Benchmark
Code
Algorithm comparison
There is a
UnstableRateTest
test scene but just in case I compared old and new algo manually, results are basically the same: