Response time hotspot vs. Method hotspot

[Yosi_Neuman]

Hi guys,

Customer showed us a trace and raised questions that we ware not able to answer and hope someone can help and spill some light on those questions.

So, here is what we see in one trace, its look like the waiting time of 1.11S under self time is the largest consumer of time in this trace.

When moving to Response time hotspots we still see the active wait time with 1.11S  and very low Network IO in terms of timing impact.

But when moving to method hotspot we see that waiting time is only consume 16% of the time and the network io raised to 82%  (when checkout the waiting thread the waiting percent is moving even lower ) 

Our questions are:

1. What is causing the flip between Response time hotspot and Method hotspot in terms of waiting and network impact?
2. From where Response time hotspot taking the wait and network io information , is it from the code as method hotspot?
3. In Response time hotspot the title says Breakdown of service exaction time and the question is if its only for the service execution part from the distribution part?

Thanks in advance for your inputs here 

@yair_mashmor & Yos 

[Marcelo_santand]

"Could you please show us a screenshot of the code level?" We could observe synchronous and asynchronous times that we were not seeing in the images. Thanks!

[Yosi_Neuman]

Hו @Marcelo_santand 

Will ask customer to get a code level screen shot.

Can the methods we see from method host spots help here?

Any how from service flow screen shot its look like most of the "heavy" transactions are synchronous  

Do we still need a screen shoot from the code level ?

Thanks 

Yos