HP UX Caliper Software manual Latency-buckets, Measure-on-interrupts, Memory-usage=, Metrics

Specifies whether to extend the callstack samples collection into kernel space. By default, both the userspace and kernelspace callstack samples will be collected. This option is used only with the cstack measurement.

--latency-buckets

--latency-buckets TrueFalse

Specifies whether or not the latency bucket information should appear in dcache measurement reports.

This option is used only with the dcache measurement.

The default value is --latency-buckets True (the information appears).

For more information, see “dcache Measurement Report Description” (page 186).

--measure-on-interrupts

--measure-on-interrupts onoffonly

Controls whether the performance monitoring unit (PMU) is enabled or disabled while processing interrupts/traps.

This option is used with the measurements that depend on the PMU for their data: alat, branch, cpu, cycles, dcache, dtlb, ecount, fprof, icache, itlb, pmu_trace, and scgprof.

on The PMU is enabled during interrupt processing, and enabled during regular processing.

off The PMU is disabled during interrupt processing, and enabled during regular processing.

only The PMU is enabled only during interrupt processing, and disabled during regular processing.

The default is on for the cpu measurement, no matter which --scopeoption you use.

For all the other measurements, the default is on if you use the --scope system option, and off if you use the --scope process option.

This option is not available on Linux. The behavior on Linux is equivalent to --measure-on-interrupts on.

--memory-usage=

--memory-usage=all[begin][:timed][:end][:PERIOD[smh]]

Controls the collection and reporting of memory usage data.

NOTE: With this HP Caliper option, you must use a qualifier or an equals sign (=). You cannot use --memory-usageas the option. You must use --memory-usage=.

If you specify --memory-usage=, then --memory-usage=all is assumed.

Use of this option causes two different sets of memory measurements to be taken, each reported in its own table in the report:

•Overall memory available (and currently in use and free) on the system

•Memory currently being consumed by the process(es) being measured by a particular HP Caliper run

For details, see “Measuring Memory Usage Concurrently with Other Measurements ” (p. 152).

--metrics

See “-m or --metrics” (p. 49).

64 HP Caliper Options