Figure 15 HP Caliper GUI
In this screen shot of the GUI, you can see that three measurement runs have already been made: two in the Before Changes project (a CPU Cycles Run and a Data Cache Misses Run) and one in the After Changes project (a CPU Cycles Run).
The application being measured is the HP C/C++ compiler, compiling the “Hello World” program. The application consists of three processes: cc, ecom, and ld.
Note that these are default measurement runs. That is, no special measurement options were used. The user entered the compile command to be measured on the Target page of the Collect view, selected the measurement to make on the Measurement page, and clicked the Start button. The requested measurement run was made and an index of the new datasets available was added to the list in the Projects view.
Selecting Performance Data to Analyze [Optional]
By default, the HP Caliper Advisor analyzes data from all of the measurement runs in the current project. This is typically what you want, so this step is optional.
If you have a special situation, there are two ways to select what performance data the HP Caliper Advisor analyzes:
•You can select one or more projects (implying all of their measurement runs).
•You can select one or more measurement runs from any project.
Selecting Performance Data to Analyze [Optional] 87