HP Caliper Advisor Rule Writer Guide

2 Running the HP Caliper Advisor
This chapter helps you get started using the Advisor.
All the information in this chapter pertains to users who will be running the Advisor,
not writing rules for it. It is a duplicate of some of the information in the chapter “Using
the HP Caliper Advisor” in the HP Caliper User Guide and is placed here for the
convenience of rule writers.
If you are already familiar with running the Advisor, you can skip ahead to “How the
HP Caliper Advisor Works” (p. 27).
Getting Started with the Advisor: Examples
To run the Advisor, you need to make one or more HP Caliper measurement runs on
an application.
Simplest Example
Assume that you have made these data collection runs:
$ caliper cpu my_app
$ caliper fprof my_app
$ caliper ecount my_app
The output databases are saved in the databases directory by default and are named
cpu, fprof, and ecount.
Then, you run the Advisor using this command:
$ caliper advise
HP Caliper looks in the databases directory for databases and produces an analysis of
all current HP Caliper runs, using all the databases in the databases directory. If no
databases are found, you receive an error message telling you that there are no runs
to analyze.
The analysis report is produced on stdout.
More Typical Examples
These examples are more typical of how you will use the Advisor.
When you first start using the Advisor, you will typically run these measurements:
• On HP-UX systems, use:
$ caliper cpu my_app
$ caliper fprof my_app
• On Linux systems, use:
$ caliper ecount my_app
$ caliper fprof my_app
Getting Started with the Advisor: Examples 19