@wu-sheng I meant binary locator, not type locator. It is really mostly about avoiding IO as it generates a bunch of garbage, especially on older VMs. The ignore matcher you refer to is exluding any type that is loaded by a class loader that fulfills a certain condition. Excluding by class loader is done before even looking at the type, therefore such exclusing is very effective. If a class loader is known to not generate any types of interest, this is a good exclusion. It will not alter the result but lead to higher performance. Especially Groovy is problematic here as it needs to generate a lot of boring filler byte code to implement its dynamic features.
[ Full content available at: https://github.com/apache/incubator-skywalking/issues/1666 ] This message was relayed via gitbox.apache.org for [email protected]
