This information is reported under Processor Information.
•Processor set (pset)
Every application can (potentially) be run in a different processor set, which can have unique characteristics that impact performance. For each process, HP Caliper detects and reports which processor set was used. Possibilities are:
◦Default: No processor set was specified.
◦Kernel: A special processor set that a few kernel processes belong to. (This appears only in
◦<pset ID>: Processor set ID number if one was specified.
This information is reported under Target Application.
The VSE components nPartitions (nPars) and Virtual Partitions (vPars) have no performance impact on applications, because applications in these environments run as they would on standalone servers. Therefore, HP Caliper does not report on these environments.
HyperThreading Information for
Information about the HyperThreading status of the processor is shown for each process in the report output. This is shown for Integruty servers
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,
•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
•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
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.
112 Controlling the Content of Reports