• 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 Melanie Z. · Feb 05, 2013 at 07:01 PM ·

Understanding Elapsed Time in Page Action Purepaths

HPage Action Preview Case 020513.dtsello, I am looking at a page action purepath which has a response time of 7671ms. The corresponding server time is 1043.58ms, client time is 0ms, and network time is 556.42ms.

Looking at the method detail, for the 3rd web request, its showing an elapsed time of 7257.79ms. Where is this elapsed time being spent? on the server side or the client side? I don't understand how he elapsed time works when looking at Page Actions and if contains server time, network time, and client time?

I've attached a screen shot and exported the purepath.

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 Melanie Z. · Feb 06, 2013 at 04:35 PM

OK I understand now that the End to End Response refers to the beakdown of Page Action Total Execution Time. But from an end user's perspective, I would think what we really care about is the Response Time, since this is what they're really experiencing. Is there a way to get a breakdown of server, network, and client time for the Response Time?

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 Melanie Z. · Feb 05, 2013 at 07:52 PM

Another question is why does the end to end response time say that server time is 66%, which equates to 5062.86ms, but then on the Server Time column, it only shows 1043.58ms?

Comment

People who like this

0 Show 1 · 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 Andreas G. ♦ · Feb 05, 2013 at 08:32 PM 0
Share

Good question. The times we show up there in the top table refer to the time breakdown of the Page Action Total Execution Time - and not the Total Response Time. Check out the Total Exec Column in the Tree. If you sum up the Exec Time for the Server-Side Requests you end up with 1043ms

The Response Time is much higher in your case - but - thats just because your page downloads a second Preview.aspx at a later point of the page life cycle

Andi

avatar image

Answer by Melanie Z. · Feb 05, 2013 at 07:43 PM

Thanks Andreas.
Does it make sense that the client time is 0? Should client time not include activities executing on the browser?

Comment

People who like this

0 Show 4 · 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 Andreas G. ♦ · Feb 05, 2013 at 08:27 PM 0
Share

The Client Time gets calculated:
Client Time = "Exec Total Time" of the Page Action - Server Time - Network Time

Exec Total Time is the time from start to end of the action that triggered the Page Action. When talking about a Page Action that was triggered by loading a page the Exec Total Time gets measured from start until the onLoad event handler is done. If it gets triggered from a JavaScript Handler, e.g: jQuery click event handler - the Exec Total Time is from start to end of that event handler.

Server Time is the time spent on the server. We take this by looking at the server side PurePath Execution Times.

Network Time is available when you have bandwidth calculation turned on. It is a calculated "estimate" of the actual time spent on the network.

So - how can it be that Client Time is 0? If there is no real client activity going on, e.g: static pages. I can see from your screenshot that you have several that show Client Time with 0. Click on it and check the PurePath - I am sure you will see server-side PurePaths that span the whole page action

avatar image Sreerag M. Andreas G. ♦ · Aug 12, 2014 at 01:33 AM 0
Share

Andi,

could we get how dynaTrace calculates network time from bandwidth.

-Sreerag

avatar image Andreas G. ♦ Sreerag M. · Aug 12, 2014 at 02:08 AM 0
Share

There is some information about this in the documentation. Start here: User Experience Management & User Action PurePaths

avatar image Sreerag M. Andreas G. ♦ · Aug 12, 2014 at 02:20 AM 0
Share

Thanks Andi.

avatar image

Answer by Andreas G. · Feb 05, 2013 at 07:25 PM

Hi Melanie

The Page Action PurePath shows all the activities for a single Page Action. This mainly includes web requests such as .aspx, .js or other resource files. The Elapsed Time indicates when a particular activity (or web request) started relativ to the Start of the Page Action.

In your case it seems that the Total Page Action took 7671ms. The first download of Preview.aspx started after 1.13ms and took 633ms. Then another resources was downloaded starting after 717ms. This can be explained because the browser first had to download the content of Preview.aspx. After parsing that HTML content it continued downloading the embedded resource from your Telerik Library. That download took 82ms. Then it seems that the browser waited for ~6450ms until it sent another request to Preview.aspx. How can this be explained? Either some long running JavaScript. Could also be something that blocked the browser from the next download, e.g: a message box prompting the user for some input, ...

What is interesting is that the onLoad event handler was triggered after 1.4 seconds and took 62ms to execute. That means that really something that was going on in the background (some JavaScript) or a waiting on a user interaction caused the browser to wait that long to send the next Preview.aspx request.

I hope this 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.

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

2 People are following this question.

avatar image 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