Figure 20 Advisor Report in the HP Caliper GUI
The individual (potential) performance issues are separated by horizontal lines. The first line of each section gives five pieces of information: the name of the executable, an index value for the issue, which category or advice class (CPU, memory, I/O, and so forth) the issue falls in, a brief description of the performance issue, and the name of the Advisor rule that detected this issue. This line is followed by from 1 to 3 sections of advice in this order: improvement, measurement, explanation.
The index value gives the relative importance of the performance issue in your application. The larger the value, the more significant the issue is. There is no meaning to the number itself; it is simply a rough way to prioritize the issues. By default, the Advisor report is sorted with the more important issues (no matter which executable they are in) listed first. The index value is thus the sort key. You can click on the column headings Executable, Index, or Class to make that item the sort key. The down arrow on a column heading indicates the sorted column.
When measurement advice is given, it includes the pages and values to change within the Collect view.
For example, consider this line:
Measurement / Measurement = Data cache misses
Sampling / Rate = 10
This advice tells you to select the Data cache misses measurement on the Collect view's Measurement page and to set the Rate field on the Sampling page to 10. Of course, you also need to have the Target page information filled in, but that should still be there from the last measurement run made.
Reviewing and Acting on the Advice 91