The Intel IPP Performance Tests are a set of command line programs used for estimating the performance of each function in the API. Each function group (or domain) has its own program for collecting performance data that allows you to test just one function, a subset of functions or all functions within the domain.
The perfsys tool is installed as part of the Intel IPP package and is located in the tools/perfsys directory. Reference performance data is installed to directory tools/perfsys/data. The tests are valid only for the system processor on which they are invoked.
For detailed instructions, descriptions of units of measurements and example output, please refer to the white paper, Measure Intel IPP Function Performance. Also refer to the tools/perfsys/readme.htm file for directions on how to use the tool.
Use the -h parameter to list the options for running the performance tests, type ps_ipps -h at the command prompt.
To run performance tests with default parameters for all signal processing functions, type ps_ipps at the command prompt and press Enter in response to all additional prompts.
Or run "ps_ipps.exe -B -v" in command line to generate an ps_ipps.csv file to include all benchmarks for funcitons in ippSP (signal processiing domain).
option B is to run batch mode
option v is to write performance result table to an .csv file format
To run a performance test for a particular function (e.g. ippsFIRLMS_32f) instead of all signal processing functions, enter the following command:
ps_ipps -f FIRLMS_32f -V firlms.csv
The output data will be stored in a file named firlms.csv.
The .csv data file contains columns with headings such as nLps, Clocks, per, and pxch. The column with the heading nLps contains the number of measured repetitions in the loop. The column with Clocks is associated with the column per or pxch, which means clocks per element ( cpe) or per pixel per channel ( pxch) respectively.
The Intel IPP package also provides test output data in directory tools/perfsys/data for your reference. Please refer to the readme.htm file for more details on this tool.