Case 1)      Hardware PMU event-based sampling analysis (User-defined)

Case 2)      User-mode sampling and tracing analysis (User-defined)

For case 1), please refer to "Event Configuration from the Command Line" article to know How-to do this analysis. The article documents information about configuring those events.

For case 2), (User-mode sampling and tracing analysis)  - when the user runs user-mode sampling and tracing analysis in command line and requests to change sample interval from 10s (default value) to 20s, with "-collect-with runss", the user should specify collectSamplesMode explicitly (with either "stack" or "nostack"). Here is an example:

$ amplxe-cl -collect-with runss -knob interval=20 --knob collectSamplesMode=stack -- ./primes.icc 
Determining primes from 1 - 100000 
Found 9592 primes 
Using result path `/home/peter/problem_report/r012runss' Executing actions 75 % 
Generating a report 
Summary ------- 
Elapsed Time: 0.992 CPU Time: 2.290 Executing actions 100 % done 
$ amplxe-cl -report hotspots -group-by function 
Using result path `/home/peter/problem_report/r012runss' Executing actions 75 % 
Generating a report 
Function Module CPU Time 
---------- ---------- -------- 
findPrimes primes.icc 2.290 Executing actions 100 % done 

 
If collectSamplesMode is not specified explicitly (with either "stack" or "nostack"), users may see the error message below. The root-cause is - with "-collect-with runss", the user should specify collectSamplesMode explicitly (with "stack" or "nostack").

$ amplxe-cl -collect-with runss-knob interval=20 -- ./primes.icc 
Determining primes from 1 - 100000 
Found 9592 primes 
Using result path `/home/peter/problem_report/r011runss' Executing actions 75 % 
Generating a report 
Summary ------- 
Elapsed Time: 0.978 Executing actions 100 % done 
$ amplxe-cl -report hotspots -group-by function 
Using result path `/home/peter/problem_report/r011runss' Executing actions 75 % 
Generating a report Result directory does not contain CPU samples. 
Executing actions 100 % done Error: Error 0x40000024 (Reporter error)

To get product updates, log in to the Intel® Software Development Products Registration Center

For questions or technical support, visit Intel® Software Developer Support

Version 2011 SP1 Initial release, September 6, 2011: release_notes_studio.pdf

When a user adopts stack-sampling collector analysis such as Hotspots, Concurrency or Locks Waits, Call Stack info will be displayed in Bottom-up report. (OS timer only)

Call Stack tree lists all call sequences (stacks) which called hot functions. Call Stacks from different threads are aggregated together for view type "Function - Call Stack", or Call Stacks can be displayed respectively for different thread for view type "Thread - Function - Call Stack".

Here is the Hotspot result after running a single thread application. Hot function foo_data_collected() has only one Stack wmain() in Bottom-up tree, but Call Stack pane indicates there are two Stacks.

First stack is wmain() from "test_itt_api.cpp:32", let's see what second stack is?

Second stack is wmain() from "test_itt_api.cpp:24". That means wmain() calls hot function foo_data_collected() from different source lines in same function. The bottom-up tree shown in the Bottom-up pane aggregates these stacks in one line. But the Call Stack pane shows each as a separate stack

Yes! The Intel(R) Parallel Amplifier is supported on Microsoft* Visual Studio* 2005/2008 - the user should create .sln file, .vcproject file in Solution Explorer.

1. Use wizard to create a new project for existing code

2. Specify project file location and project file name (it could be same as your EXE file)

3. Add existing item (EXE file) to current project

4. Manually create "Debug" folder under project file location.

5. Manually copy all EXE/DLL files and PDB files to the "Debug" folder

6. Ensure that you can run "Debug\Start Without Debugging" in Microsoft* Visual Studio*, then you can run Intel(R)Parallel Amplifier.

The Parallel Inspector and the Parallel Amplifier have new options (plug-in) in Microsoft* Visual Studio* 2005/2008's  "Options" dialog, please see "Result Location" item under "Intel Parallel Inspector" and "Intel Parallel Amplifier", change it from "Save results in the Visual Studio* project default location" to "Save results in the directory:". Note that the user should specify a directory which already is existed.



2. Sometime the user starts the Parallel Inspector Analysis or the Parallel Amplifier Analysis, meanwhile the user wants to see separated Console application's running. The user can simply modify "Direct output for non-GUI application to:" from "Separate console windows" to "Microsoft* Visual Studio* output window".

After doing above change, the use can watch Analysis status and Console application's running simultaneously.