caliper.1 (2010 09)

c
caliper(1)
Integrity Systems
caliper(1)
(Requires Optional HP Caliper Software)
Options
There are a number of command line options available which alter
caliper’s operation. Option names
and literal arguments can be abbreviated to their shortest, non-ambiguous spelling. Although the com-
mand line synopsis above shows
caliper options following measurement , in reality they can precede
and/or follow it.
In the option descriptions below, lower-case text (computer/bold font) is a literal which is typed as shown
and upper-case text (italics or underline font) is descriptive and must be replaced with real values.
See PLATFORM-SPECIFIC ADDENDA below for additional options that may be available.
The following option can be used to supply
caliper options from a text file:
--options-file=
OPTIONS_FILE or -f=OPTIONS_FILE
Specifies a text file (OPTIONS_FILE) containing a list of
caliper command-line options
(separated by spaces or newlines). You can also use an options file to specify a
caliper measure-
ment configuration file as well as the application to be profiled and its arguments.
Data Collection Options
The command line options which affect data collection are:
--branch-sampling-spec=
EVT_PERIOD[
,VARIAT ION [,CPU_EVENT [:EVENT_PARAM]...]]
Controls the branch sampling rate for an
scgprof collection. See the --sampling-spec
option
below for argument details.
--cstack-sampling-spec=
TIME_PERIOD
Controls the sampling rate of the call stack profile
(cstack) collection in the overview measure-
ment. This option is valid only when using the overview measurement. See the --sampling-
spec option below for argument details.
--database=DATABASE[,unique]
(Can also be specified with the -d option.)
This saves measurement results to the named database.
Performance data is always saved to a
caliper database, whether one is explicitly specified or not.
If the
--database option is used to specify the explicit name and location of the database, then
that database is used.
If the
--database option is not given, then a database (named for the type of measurement made)
will be saved in the ./.hp_caliper_databases
directory (this default can be changed with the
CALIPER_DATABASES
environment variable). The most recently created measurement database
is pointed to by an automatic "latest" symlink in the
CALIPER_DATABASES
directory.
The optional
unique qualifier will append the process ID of the HP Caliper process to the name of
the database it is writing to, e.g., mydb-21952.
--dcache-data-profile
Valid only for the dcache measurement, this option specifies that caliper should additionally
record (and report) global variables and process regions (stack, heap, data, etc.) associated with
data cache misses.
--dcache-sampling-spec=
EVT_PERIOD[,VARIATION[,CPU_EVENT [:EVENT_PARAM]...]]
Controls the sampling rate of the data cache miss profile (dcache) collection in the overview
measurement. This option is valid only when using the overview measurement. See the
--sampling-spec option below for argument details.
--db-save=[syms][:code][:src][:all]
Specifies that additional information about each load module seen at collection time is to be saved
into the HP Caliper database. This allows Caliper to correctly attribute displayed data, even if the
load modules are not available when a report is requested.
syms Tells Caliper to save off symbol information about each load module into the database.
code Saves off the executable text segment of each load module into the database; this argument
also implies the syms argument.
src Specifies that source line attribution data for each load module should be saved into the
database; this argument also implies the code and syms arguments.
HP-UX 11i Version 3: September 2010 − 5 − Hewlett-Packard Company 5