Faster type matching

[laurit]

Figuring out which types need to be transformed is quite costly. Measuring the time spent in

opentelemetry-java-instrumentation/javaagent-tooling/src/main/java/io/opentelemetry/javaagent/tooling/bytebuddy/LoggingFailSafeMatcher.java

Lines 44 to 51 in 7b842fe

	public boolean matches(T target) {
	try {
	return matcher.matches(target);
	} catch (Throwable e) {
	logger.log(Level.FINE, description, e);
	return false;
	}
	}

while starting Liferay

LoggingFailSafeMatcher#match count=25981347, time=9796ms

This pr decomposes matchers with reflection and divides them into 3 categories: matches by class name, matches by class name in hierarchy, something else. The 3rd category has about 10 matchers. Transformer list inside byte buddy is replaced with a proxy that when we know that current class isn’t going to match any of the name or hierarchy matchers just returns the matchers from the 3rd category. Because we can get the super type names in defineClass we can quickly tell whether there is a hierarchy matcher that applies to given class.

LoggingFailSafeMatcher#match count=1100249, time=3498ms

[mateuszrzeszutek]

👍