dotTrace 2016.1 Help

Profile ASP Web Site

Typically, determining performance issues in a web application is required when it is already running on a server. In this case, you have two options:

  • Profile the app remotely. No dotTrace on the server is required.
  • Profile the app locally on the server. dotTrace must be installed on the server.

Note that in both cases, to perform profiling you must have administrative rights on the web server.

To remotely profile an ASP web site hosted on a IIS server:

  1. On the web server, do the following:
    • Copy the RemoteAgent.zip archive from the dotTrace installation directory on your local computer (by default, C:\Users\[username]\AppData\Local\JetBrains\Installations\dotTrace[N]) to any directory on the server.
    • Unpack the archive on the server.
    • Start RemoteAgent.exe from the console on the server.
    • Ensure that inbound connections to Remote Agent are not blocked by the firewall.
  2. On the local computer, run dotTrace as a standalone application. The dotTrace Home window will open.
  3. In the right panel, choose the New Session | Remote tab.
  4. In the central panel, specify the address of the remote agent service in Remote Agent URL.
    By default, the URL is net.tcp://[remote_computer_IP_address]:9100/RemoteAgent.
  5. Click Connect to establish connection with the remote host.
  6. In the central panel, in Attach to Process select the w3wp.exe process that corresponds to the app pool running the profiled application.
  7. In the right panel, in Profiler Options, specify profiling type. When attaching the profiler to a process, you can choose only between Sampling (evaluate performance and determine slowest methods in your app) and Timeline (determine slowest methods and how method calls are distributed in time).
    For more details on profiler options, refer to the Profiler Options section.
  8. Click Run.
  9. Collect profiling data (snapshots). For more details on how to control profiling session, refer to Controlling Profiling Session.
  10. After you collect the data, detach the profiler from the app pool using the Detach button of the Controller window.
  11. Analyze the collected snapshots either in the Performance Viewer or Timeline Viewer (depends on the profiling type you select).
    Note that as you profile an app pool, you will see large amount of native code in the snapshot.

To locally profile an ASP web site hosted on a IIS server:

  1. Install dotTrace on the web server.
  2. Run dotTrace as a standalone application. The dotTrace Home window will open.
  3. In the right panel, choose the New Session | Local tab.
  4. In the central panel, in Profile Application select IIS.
  5. In the right panel, in Application Options, turn on Open URL and specify the URL of the profiled application. If you do not do this, dotTrace will start profiling of the first running application pool.
  6. In the right panel, in Profiler Options, specify profiling type.
    For more details on profiler options, refer to the Profiler Options section.
  7. Click Run. Note that after you do this, the IIS service and, as a consequence, the profiled application pool will be restarted.
  8. Collect profiling data (snapshots). For more details on how to control profiling session, refer to Controlling Profiling Session.
  9. After you collect the data, detach the profiler from the app pool using the Detach button of the Controller window.
  10. Analyze the collected snapshots either in the Performance Viewer or Timeline Viewer (depends on the profiling type you select).
    Note that as you profile an app pool, you will see large amount of native code in the snapshot.
Last modified: 19 August 2016