DX Application Performance Management

  • Private Community

  • 1.  ASP.NET Request Execution Time

    Posted Dec 14, 2015 04:32 PM

    Hi,

     

    How to trace the exact request that is taking long period to execute?

    This metric sometimes goes into minutes but not able to figure out what is the actual request that is taking this long time to execute.

    Any ideas where to look for?

     

    --

    Regards,

    Arjun



  • 2.  Re: ASP.NET Request Execution Time

    Broadcom Employee
    Posted Dec 14, 2015 05:51 PM

    Hi Arjun,

    If I am not mistaken that is a high level Perfmon Collector metric?

    To drill down into specific app performance you need to use the Investigator (Metric Browser) or WebView to examine Average Response Times for your .NET apps and then you can drill into the high ones in more detail using Transaction Trace etc

    The Metric Browser Tab - CA Application Performance Management - 10.1 - CA Technologies Documentation

    Using the Transaction Tracer - CA Application Performance Management - 10.1 - CA Technologies Documentation

     

    Monitor Application Health and Performance - CA Application Performance Management - 10.1 - CA Technologies Documentatio…

     

    Hope this helps

    Regards,

    Lynn



  • 3.  Re: ASP.NET Request Execution Time

    Posted Dec 15, 2015 03:13 PM

    Hi Lynn,

     

    Unfortunately nothing is reporting in Transaction Trace viewer related to that high execution times ( most of the traces related to backend calls are in msec which is good) and Response times seems to be well with in normal range.

    I should tell you this dotnet application is a custom build mostly centered around querying backend db. There is a page with dropdowns to select some options and up on submit, it will present you some output. There is no frontend node reporting only backends are visible.

     

    Upon some investigation I found that it has something to do with the session termination because as there is no logoff option on page, I am thinking when we close the browser to exit the page and launch it after some while at this moment the REquest Execution Time is started reporting with value = time since the page launched previously + till browser closed.

     

     

    1.png2.png3.png

     

    --

    Regards,

    Arjun



  • 4.  Re: ASP.NET Request Execution Time

    Broadcom Employee
    Posted Dec 15, 2015 06:14 PM

    Hi Arjun,

    Thanks for the update. That is interesting.

    I found this MS page:

    Chapter 15 - Measuring .NET Application Performance

    ===

    ASP.NET\Request Execution Time

    Threshold: The value is based on your business requirements.

    Significance: This is the number of milliseconds taken to execute the last request. The execution time begins when the HttpContext for the request is created, and stops before the response is sent to IIS. Assuming that user code does not call HttpResponse.Flush, this implies that execution time stops before sending any bytes to IIS, or to the client.

    ===

    So perhaps if the client/browser just goes away the response is never sent and the counter is not flushed until browser (with same session id) comes back?

     

    In summary it sounds like the application itself shows no health problems and it is just the way that this perfmon counter behaves for this scenario.

     

    Regards,

    Lynn



  • 5.  Re: ASP.NET Request Execution Time

    Posted Dec 16, 2015 05:01 PM

    Looks to be the case Lynn!

     

    Application seems working fine. No issues reported.

     

    --

    Regards,

    Arjun