refactor(metrics): optimize addDimensions
method to avoid O(n²) complexity
#4156
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.
Summary
Changes
Replace
Object.assign
usage indimensionSets
reducer with direct property assignment to improve time complexity from O(n²) to O(n). The previous implementation copied all accumulator properties on each iteration, while the new approach mutates the accumulator directly using afor...of
loop.This change maintains identical behavior while significantly improving performance for metrics with multiple dimension sets, especially in high-throughput Lambda functions.
This PR addresses a performance bottleneck in the Metrics utility where
Object.assign
was used in a reducer pattern, causing O(n²) time complexity. The fix follows the established coding guidelines that recommend avoidingObject.assign
in accumulators and usingfor...of
loops instead.Issue number: Fixes #4155
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.