Only build property key path on construction #3040
Merged
+7
−9
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.
Issues
Performance improvement
Description
Currently, PropertyKey path is built on every call to PropertyKey.getPath() and performs regex match. This can be expensive and redundant as when we add a listener, we loop through the existing handlers and call propertyKey.getPath() for every handler that exists. The performance hit will be most noticeable in clusters with a large instance count.
Technically, this will make it so that PropertyKey.getPath() will no longer update after instantiation if the underlying PropertyPathBuilder's templateMap is updated. However, I did not find this being done anywhere in the code so in effect there should be no change
Flame graph from 5 minute CPU profile taken during controller transiting to LEADER for clusters with thousands of instances.
Tests
None
N/A
Commits
Code Quality
(helix-style-intellij.xml if IntelliJ IDE is used)