topic Re: Profiling a .NET Windows Service in Analyzers

Profiling a .NET Windows Service

sureshk — Thu, 08 Apr 2004 01:25:59 GMT

Is it possible to profile a Windows Service written using .NET using VTune? Thanks.

-Suresh

Re: Profiling a .NET Windows Service

Anonymous24 — Thu, 08 Apr 2004 03:06:31 GMT

sureshk:

Sampling can be used on any code that runs on the system: application, driver, service, etc. As long as you have debug information for the module (i.e., exe, dll, etc.), the analyzer can display hotspots within your code.

To use call graph on a Windows service, there are special instructions. Please see http://support.intel.com/support/performancetools/vtune/sb/cs-006207-prd232.htm.

-dlanders

Re: Profiling a .NET Windows Service

James_P_Intel — Fri, 13 Apr 2007 01:01:13 GMT

The above link does not work.

Re: Profiling a .NET Windows Service

aokunev — Thu, 17 May 2007 13:42:20 GMT

Hi

http://www.intel.com/support/performancetools/vtune/v71/sb/cs-009677.htm is the correct one. It was the first in google search for 'call graph windows service'. There were no big changes in .NET related functionality, so there are chances the document is relevant for 9.0 as well.

regards, Andrei

Re: Profiling a .NET Windows Service

jbuxtonval — Wed, 09 Apr 2008 00:24:01 GMT

That link isbroken too. Search seems useless.

Re: Profiling a .NET Windows Service

David_A_Intel1 — Thu, 10 Apr 2008 22:56:44 GMT

It's here.

Also, looks like we archived that original article (it has been 4 years, after all! :-}. Here is the content for reference:

Symptom:
No data is collected when I try to call graph my Windows* service.

Solution:
The Intel VTune analyzer, by default, does not have administrative privileges to access Windows services. Follow the steps listed below to enable the analyzer:

Make sure that you are logged in as Administrator on the system.
Make sure that your service is installed and registered correctly.
Open the Services applet (in Administrative Tools) and find your service in the list of installed services.
If your service is running, stop it.
Depending on your OS, click on the Startup button or right-click the service and select Properties, and change the StartUp type to Manual.
Change LogOnAs to This Account and type "Administrator" in the This Account text box.
Enter the password for the Administrator account. This will enable the analyzer to access the service when the activity is started.
Confirm the password.
Confirm that the service can be manually started and stopped.

The service cannow be call graphed using the following steps:

Start the analyzer and select the Call Graph Wizard.
Select Win32*/Win64* Profiling and press Next.
Select No application to launch and press Next.
Add your service to list of Modules of Interest and press Finish.
Run the activity. When activity is run, the analyzer should instrument your service and prompt you to start the service.
Start the service. The analyzer detects that the service has started and starts call graph analysis.
Use the service - exercise the service by whatever means you have developed.
Stop the service.
Now, manually stop the analyzer activity by pressing the Stop button. The analyzer should produce a call graph for the selected service.