• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Pierre D. · Oct 08, 2014 at 05:31 PM ·

Meaning of breakdown by execution time

hello, it s a bit of a puzzle signification of caller breakdown.

In the screenshot below, we can see the Engine$2.run() method takes 46.09s, and if we have a look on caller breakdown we can see who is calling it.

We have also the breakdown of CPU (59%) and IO (41%).

But what does it means ?

I don't think it is just at this method level (I mean just within this method, excluding callee) than 27 s are spent in processing (59% of 46 s) and 19 s are spent in io (41 % of 46 s).

I guess it is the time spent from this method, including callees. But in this case why all those information are linked to this method and not for instance at the caller method just above ? In other world what is the business rule to detect those values and assign them to a method level.

 

Pierre

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

4 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Pierre D. · Oct 08, 2014 at 10:35 PM

yep, I've got it.

Thanks Andreas (smile)

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Oct 08, 2014 at 10:33 PM

Its because every time when we take our Auto Sensor Snapshots (looking at current stack trace) we always saw Engine$2.run as the current executing method and not OriginatorExecutionService.

You can drill from here to the PurePath - this will also show you that the time is booked on Engine2 becuase thats the method that was at the end of the Snapshot we took

Makes sense?

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Pierre D. · Oct 08, 2014 at 10:16 PM

Hi Andreas,

so it means Engine$2.run() took being executed 46.09s j, including the methods called inside this method.

But why Dynatrace count this time at Engine2$run() and not at OriginatorExecutorService$2.run() ?

Is it due to the stacktrace taken often by Dynatrace to count the time spent in method ? in this case most of stacktrace done concern the Engine$2.run ?

 

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Oct 08, 2014 at 09:57 PM

Hi Pierre

It means that dynaTrace saw the Engine$2.run method being executed 46.09s in the selected time interval, e.g: the last 30 minutes

Whenever we see the method executed we capture in which state the method is, e.g: is it executing code (=CPU), is it waiting for someting (=Wait), is it waiting for a sync bloc (=Sync) or is it doing something else (=IO). In your case the run method itself was seen exeucting code in 59% of the time. The rest was I/O activity. It really means that this method spent that time in CPU & I/O. The caller breakdown shows you who actually called that method

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

1 Person is following this question.

avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A