Visible to Intel only — GUID: GUID-5182CA3D-F4C2-482E-8064-7D5B50D5F448
Visible to Intel only — GUID: GUID-5182CA3D-F4C2-482E-8064-7D5B50D5F448
Dialog Box: Project Properties - Analysis Target
Purpose
Use this tab to specify the target executable, set important project properties, and review current project properties.
Always check project property values before analyzing a new target.
Location
Analysis Target tab is located in the Project Properties dialog box.
To access the Project Properties dialog box, do one of the following:
- Click the
button on the main toolbar.
- Choose File > Project Properties....
- Press Ctrl+P.
Controls
In the Analysis Target tab, select an analysis type from list (on the left) to display and configure project properties.
The following table covers project properties applicable to all analysis types. To view controls applicable only to a specific analysis type, use the links immediately below:
Common Controls
The following controls are common for all analysis types. Specify the properties in the Survey Hotspot Analysis tab and check that the Inherit Settings from the Survey Hotspots Analysis Type checkbox is enabled in other tabs to share the properties for all analyses.
Use This |
To Do This |
---|---|
Target type drop-down |
If you choose Attach to Process, you can either inherit settings from the Survey Hotspots Analysis Type or specify the needed settings. |
Inherit settings from Visual Studio project checkbox and field (Visual Studio* IDE only) |
Inherit Intel Advisor project properties from the Visual Studio* startup project (enable). If enabled, the Application, Application parameters, and Working directory fields are pre-filled and cannot be modified.
NOTE:
In Visual Studio* 2022, Intel Advisor provides lightweight integration. You can configure and compile your application and open the standalone Intel Advisor interface from the Visual Studio for further analysis. All your settings will be inherited by the standalone Intel Advisor project.
|
Application field and Browse... button |
Select an analysis target executable or script. If you specify a script in this field, consider specifying the executable in the Advanced > Child application field (required for Dependencies analysis). |
Application parameters field and Modify... button |
Specify runtime arguments to use when performing analysis (equivalent to command line arguments). |
Use application directory as working directory checkbox |
Automatically use the value in the Application directory to pre-fill the Working directory value (enable). |
Working directory field and Browse... button |
Select the working directory. |
User-defined environment variables field and Modify... button |
Specify environment variables to use during analysis. |
Managed code profiling mode drop-down |
|
Child application field |
Analyze a file that is not the starting application. For example: Analyze an executable (identified in this field) called by a script (identified in the Application field). Invoking these properties could decrease analysis overhead.
NOTE:
For the Dependencies Analysis Type: If you specify a script file in the Application field, you must specify the target executable in the Child application field. |
Modules radio buttons, field, and Modify... button |
Including/excluding modules could minimize analysis overhead. |
Use MPI launcher checkbox |
Generate a command line (enable) that appears in the Get command line field based on the following parameters:
|
Automatically stop collection after (sec) checkbox and field |
Stop collection after a specified number of seconds (enable and specify seconds). Invoking this property could minimize analysis overhead. |
Survey Analysis-Specific Controls
Use This |
To Do This |
---|---|
Automatically resume collection after (sec) checkbox and field |
Start running your target application with collection paused, then resume collection after a specified number of seconds (enable and specify seconds). Invoking this property could decrease analysis overhead.
TIP:
The corresponding CLI action option is --resume-after=<integer>, where the integer argument is in milliseconds, not seconds. |
Sampling Interval selector |
Set the wait time between each analysis collection CPU sample while your target application is running. Increasing the wait time could decrease analysis overhead. |
Collection data limit, MB selector |
Set the amount of collected raw data if exceeding a size threshold could cause issues. Not available for hardware event-based analyses. Decreasing the limit could decrease analysis overhead. |
Callstack unwinding mode drop-down list |
Set to After collection if:
|