-
When we conducted stress tests on some interfaces, we found that the interface latency would occasionally increase. Finally, it was found that it was blocked at the getLoader method, and this occurred after the introduction of the javaagent. What could be the cause of this?
This will result in high time consumption for some Tomcat threads |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
I'd guess that your application is creating a new class loader and loading new classes on each request. For every class loader instrumentation tries to figure out which instrumentations could apply. This involves doing resource lookups, which can be expensive. What version of the agent are you using? If it is 2.x have you enabled any of the instrumentations that were disabled by default? |
Beta Was this translation helpful? Give feedback.
We could ignore
com.alibaba.fastjson.util.ASMClassLoader
#11954 that should resolve the issue. Though if new instances ofASMClassLoader
are being created it could also very well be a bug in your application (are you creating newSerializeConfig
instances?) or something completely different.