Improve performance of JdkDynamicAopProxy.getProxy(ClassLoader) #25660
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.
Hello, while profiling workload that creates lots of projections I've found out that about 33% of

ProxyFactory.getProxy()
are taken byJdkDynamicAopProxy.findDefinedEqualsAndHashCodeMethods
, see attachment:The hot spot is here:
It looks like we don't need to call either
JdkDynamicAopProxy.findDefinedEqualsAndHashCodeMethods
, orAopProxyUtils.completeProxiedInterfaces()
at each invocation ofJdkDynamicAopProxy.getProxy
, because their results don't depend onClassLoader
argument and can be calculated only once at obejct construction time, alsoadvised
field is declared final.Also related methods of
ReflectionUtils
could also be trivially improved.