1. Open the Executable Settings dialog box, or click Settings in the Run Program dialog box.
2. Select the PowerTune tab.
3. Select whether to use Line, Function, or Time as the default measurement type, each time you run the selected program.
Note:
The PowerTune tab displays either the fields for native-compiled (unmanaged) code or the fields for Managed code, depending on the executable for which you are making settings.
4. For native-compiled code, select an instrumentation mode to specify the modules to instrument:
§ To use inclusive instrumentation. select All Modules.
Select also whether to time all modules in the Windows directories. By default, Quantify times these modules instead of using the specified default measurement type, to improve the run-time performance of programs during profiling.
Click the Configure... button following All Modules to specify how to measure specific modules.
§ To use selective instrumentation, select Selected Modules.
To select modules for instrumentation and to specify measurement types and instrumentation states for modules, click the associated Configure... button. Modules must have debug information, and .exes must also have relocation data.
5. For .NET managed code, inclusive instrumentation is the default. To use selective instrumentation for Managed, click Configure... to specify the classes you want to profile.
Notes:
§ All data that Quantify collects for .NET managed code is collected by timing, at both the line and function level.
§ The Time measurement type is not supported when you are profiling native-compiled programs using selective instrumentation.
§ If you choose to time functions in an executable, the only data Quantify includes for the executable is the .exe's entry point. The entry point's function time includes the function time of the other functions in the .exe.
§ Quantify uses debug line information to collect line-by-line performance data. If debug line information is not available for a module, Quantify times that module.
§ For native-compiled (unmanaged) programs, Quantify also requires relocation data to collect data at line or function level. If relocation data is not available for an .exe, Quantify times the functions. For a DLL, only data for exported functions is recorded. Time for internal, non-exported functions is attributed to the calling exported functions.
§ Some system modules are always timed.
§ For changes to the measurement type to take effect, you must rerun the program.
§ Quantify saves settings for the current program in the Exename_pure.ini file. These settings apply each time you run the selected executable, until you change a setting. To set default settings that apply to all programs, use the Default Settings dialog box.
(C) Copyright IBM Corporation 1993, 2009.