Question

Screenshots of the call tree and hot spots in the CPU View when profiling my application are given below. Can I say that cglib's MethodInterceptor.intercept() is a hotspot? It's not code that I wrote or even calling it directly, it's grails internal call. If yes, how do I fix it?

I know I should generally be looking at only the "Runnable" thread status. But, this only shows as a hotspot when the thread status is set to "Waiting" or "All States". Does that mean intercept() is waiting for some event to occur? How come it's this same method that's waiting in all the flows? And how to fix this issue?

Call Tree:

Hot Spots:

Was it helpful?

Solution

There are non-profiled classes between MethodInterceptor and OrderService. Try to switch to "Sampling" and disable all filters, then look at the hot spots view again.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top