HP Caliper User's Guide

3. All the databases are scanned for executable objects to analyze that match the
selection criteria. By default, all objects with performance data are analyzed.
Alternatively, you can use the --analysis-focus option or the
analysis_focus variable in the .caliperinit file to choose specific objects
to analyze. If multiple versions of the same object exist, the one with the most
recent modification date/time is chosen and the older versions are ignored. The
list of objects to analyze is now sorted in alphabetic name order.
If the Advisor cannot find any of the requested objects in the databases given, the
run terminates with an appropriate message.
4. For each executable object to be analyzed, all consistent performance data for that
object is identified within the databases. To be consistent, only performance data
that was collected on the same type of system (operating system, processor type,
and processor speed) is used. The first measurement instance of each analysis
object is used as the system type to match. Performance data collected on a different
type of system is not used in the analysis.
5. All the specified rule files are read and precompiled in the order given by the
--rule-files option or the rule_files variable in the .caliperinit file.
If no rule files are provided, then the default rule file is used.
Each rule file is a Python script containing one or more independent rule functions.
When called later, each rule function retrieves the needed performance data for
the object being analyzed, makes decisions about a possible performance problem,
and, if appropriate, generates one or more advice messages.
6. For each application object to be analyzed, a new report is started, all rule functions
are called for that one object, and all applicable advice is gathered, sorted, and
printed.
112 Using the HP Caliper Advisor