Made ParentClass reflection resolving lazier #2584
Merged
+34
−28
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.
before this PR we looked up the whole parent class hierarchy, even though we work thru the results one by one and early exit on success. this means we are doing more reflection then necessary.
perf comparison
with 1.10.x@6754c2308
with this PR:
its not a huge win, but I think the improvemnt adds up as more worker processes are started, as every worker has some overhead in doing too much reflection.
we could even consider marking
getParents()
as@deprecated
, to make sure other 3rd party rules/extension don't do overaggressive reflection?