ref(metrics): Move max aggregator size into config and allow passing now timestamp for merge #3904
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.
The
max_total_bucket_bytes
config can be just part of the aggregator, it's always passed as an argument with the same value and the project max size is already part of the aggregator.Additionally improves performance by not re-creating the
now
timestamp over and over again when merging a large batch of metrics into the aggregator. This takes up a significant amount of time.#skip-changelog