HP Caliper User's Guide

Possible status outputs are:
• Not available on this system: The processor is capable of HyperThreading, but the
operating system used does not support it. A newer operating system (for example,
HP-UX 11.31) is needed.
• Disabled in firmware: The processor and operating system are capable of
HyperThreading, but it was disabled by the firmware.
• Off for this process: The processor and operating system are capable of
HyperThreading, and it was enabled by the firmware, but it was turned off for
the processor set that this process was run in. Note that there can still be a negative
performance impact on a process when HyperThreading is firmware-enabled but
off.
• On for this process: The process was run in a processor set that had HyperThreading
turned on. There will be a performance impact on the measured process.
• Unknown status: The status could not be determined. (This applies only to a few
special HP-UX kernel processes and only in system-wide measurements.)
This information is reported under Target Application.
In addition, some HP Caliper measurements provide data on the impact of
HyperThreading. Specifically, the alat, cycles, ecount, and fprof measurements
show two PMU events related to HyperThreading:
• CPU_OP_CYCLES.ALL — The number of elapsed CPU operating cycles. When
HyperThreading is on, this is the number of elapsed CPU operating cycles used
by only this process's hyperthread.
• CPU_OP_CYCLES.ALL:all_threads=true
The number of elapsed CPU operating cycles used by both hyperthreads. Available
only when HyperThreading is on.
And these measurements provide the “% Core cycles due to this thread” derived metric.
This metric tells you what percentage of the available processor cycles were consumed
by the measured process.
How HP Caliper Saves Data in Databases
HP Caliper saves performance data for every measurement run to a database. This
allows you to regenerate reports from the same performance data without having to
rerun your application under HP Caliper. You have these capabilities:
• You can generate a new report with different attributes from the saved data. This
means that you do not have to rerun HP Caliper on the live program.
• When you save the results to a database, you can create a snapshot of the program
results to compare with subsequent versions of your program. This lets you
compare the results of changes to your program.
• You can merge the results of two or more databases.
• You can compare (“difference”) the data collected in two databases.
How HP Caliper Saves Data in Databases 147