chore(source/crd): optimize endpoint labels without looping over #5492
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.
What does it do ?
Relates #5243
Motivation
Working with CRD, I found that labels applied in a loop, such as ResourceLabelKey. The flow looks like that
Let:
Then:
Outer loop: n
Inner loop: m (per .Spec.Endpoints)
Nested call: setResourceLabel includes another loop of k
Overall time complexity:
O(n * m + n * k)
With this tweak, reducing time complexity to
O(n * m)
. Not a massive gain, but still.follow-up:
ResourceLabelKey
or setting them in a loop.More
switch to more efficient string slicer