HP-UX Reference (11i v2 07/12) - 1 User Commands A-M (vol 1)

c
caliper(1)
For Integrity Systems Only
caliper(1)
Caliper 4.3 Caliper 4.3
(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 measurement
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[,VARIATION[,CPU_EVENT[:EVENT_PARAM]...]]
Controls the branch sampling rate for an
scgprof collection. 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.
--data-summary
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.
--duration= ELAPSED_TIME
(Can also be specified with the -e option).
Specifies how long the measured application should run (in seconds) before caliper stops measur-
ing it. When
caliper stops measuring, the application is resumed and runs freely.
--event-defaults=EVENT_PARAM[:EVENT_PARAM]...
Specifies the default CPU event parameters. These apply to all CPU events unless an event-specific
setting is provided for the given parameter.
EVENT_PARAM is defined as:
[{
privilege-level-mask|PLM}=]{all|user|kernel}|{
threshold|T}=THRESHOLD
PLM determines the privilege level setting for a given metric. By default, metrics are measured when
your application runs in user space. The privilege levels available are:
user, kernel, and all.
THRESHOLD is an integer value that determines the semantics of the counts reported by HP
Caliper. When the threshold is zero (the default), the reported count is the number of occurrences of
the event. When the threshold is not zero, the reported count is the number of CPU cycles during
which the number of occurrences of the event met or exceeded the threshold.
--frame-depth=COUNT
Valid only for the cstack measurement, this option specifies the maximum number of frames to
HP-UX 11i Version 2: December 2007 Update − 5 − Hewlett-Packard Company 95