About Filtering Performance Data

Related Topics

Quantify uses global filters to remove data for non-critical functions in system libraries and other program modules before it displays the performance data for the program you're profiling. Quantify's global filters are contained in the filter file Quantifyw_exe.qft.

As you analyze the performance data, you can create additional filters by using the Filter Manager dialog box or by using the Filter commands on the shortcut menu in the Call Graph, Function List, and Function Detail windows. For example, you can filter data by module, by function (for example, functions with CWnd in their name), or by measurement type (for example, all waiting and blocking functions). When you create new filters, Quantify saves the filters with the existing filters in the Quantify filter file (.qft) Exename_exe.qft.

You can also create filter files for specific modules, such as DLLs, to use whenever you profile a program that uses that module. For more information, click images\shortcut.gif

When you run from the command line and save performance data to an ASCII text file, Quantify also provides a command-line option for controlling the use of filters. This is especially useful in test harnesses or scripts. For example, the following line instructs Quantify to profile the program Hello.exe, then save the output to a text file using the filters contained in the filter file Test_harness.qft:

quantify /SaveTextData /FilterFiles=test_harness.qft hello.exe

Notes:

§      For details about .ini file names and their locations, click images\shortcut.gif

§      The Quantify provides different sets of global filters for profiling Visual C++ and Visual Basic programs.

(C) Copyright IBM Corporation 1993, 2009.