You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, methodDeclaringClassName of * (especially in conjunction with methodName of * and methodParameterTypes of ..) causes a heavy burden on instrumentation checking and retained memory in AnalyzedWorld.java for tracking potential matches (even though the instrumentation will only be applied to subclasses of className).
This should be optimized by matching methodDeclaringClassName only against subclasses of className when it is a pattern, and against superclasses (in order words against all classes) when it is not a pattern, e.g. see AsyncHttpClientAspect.java.
This will break at least one current use (e.g. ResultSetAspect.java) but this one in particular should be easy to re-write using two pointcuts instead of using the | pattern.
The text was updated successfully, but these errors were encountered:
Currently,
methodDeclaringClassName
of*
(especially in conjunction withmethodName
of*
andmethodParameterTypes
of..
) causes a heavy burden on instrumentation checking and retained memory in AnalyzedWorld.java for tracking potential matches (even though the instrumentation will only be applied to subclasses ofclassName
).This should be optimized by matching
methodDeclaringClassName
only against subclasses ofclassName
when it is a pattern, and against superclasses (in order words against all classes) when it is not a pattern, e.g. see AsyncHttpClientAspect.java.This will break at least one current use (e.g. ResultSetAspect.java) but this one in particular should be easy to re-write using two pointcuts instead of using the
|
pattern.The text was updated successfully, but these errors were encountered: