Hitachi

JP1 Version 12 for UNIX Systems JP1/Performance Management - Agent Option for Platform Description, User's Guide and Reference


CPU - Per Processor Detail (PI_CPUP)

Organization of this page

Function

The CPU - Per Processor Detail (PI_CPUP) record stores the performance data per unit time on the processor usage. Every time performance data is collected, a record is created for each processor. This is a multi-instance record.

If you are collecting processor performance data from the results output by the sar command in the AIX environment, the displayed values will be for different fields. For details about the values displayed in the fields when collecting processor performance data from the results output by the sar command in the AIX environment, see 2.3.23 Monitoring processor performance based on results output by the sar command in an AIX environment.

Note:
  • If the DLPAR function of AIX, the vPars function of HP-UX, the DR function of Solaris, or the CPU hotplug function of Linux is used to modify a system resource while a PFM - Agent for Platform service is running, some types of performance data cannot be correctly collected. The table below shows the types of system resources that are affected and the actions that you can take to correctly display reports after the modification:

    System resource type

    Report type

    Actions to be taken after modification

    CPU

    Real-time

    Display the report again.

    Historical

    Specify the display period such that it does not include the date and time when the system resources were modified.

    Fields other than those listed below are affected by a system resource modification:

    • Interval (INTERVAL)

    • Record Time (RECORD_TIME)

    • Record Type (INPUT_RECORD_TYPE)

    • Fields that are added only when data is recorded in the Store database

    For details about modifying system resources, see Notes on performance information when modifying system resources in Notes on records.

  • In AIX, when the Status field of CPU - Per Processor Detail (PI_CPUP) record is changed from operating CPU to non-operating, since the operation duration exists in between the collection interval, [Online] is displayed at the time of the next collection after the change. After that, if the CPU state is not changed, it is further displayed as [Offline] during next collection time.

  • If you collect in a non-global zone environment of Solaris, the value of the Boot Time field might not be displayed correctly.

    Display example: 1970 01 01 06:00:00

Default values and values that can be specified

Item

Default value

Modifiable

Collection Interval

60

Yes

Collection Offset#

0

Yes

Log

No

Yes

LOGIF

Blank

Yes

Over 10 Sec Collection Time

Yes

No

Realtime Report Data Collection Mode

Reschedule

Yes

#

A value between 0 and 32,767 seconds can be specified (a value within the range specified for Collection Interval). Use this item to distribute the collection load, because executing data collection all at once results in concentration of the processing workload. Note that the data collection duration to be recorded is the same as the Collection Interval, regardless of the value specified for Collection Offset.

When changing the Collection Offset value, specify a value that takes into account the impact of the collection processing load.

ODBC key fields

PI_CPUP_LOGICAL_PROCESSOR_ID

Lifetime

None

Record size

Fields

PFM-View name

(PFM-Manager name)

Description

Smry

Format

Delta

Not sprtd in

Data source

Boot Time(SYSTEM_BOOT_TIME)

The last boot time

COPY

time_t

No

--

--

CPU %(KERNELMODE_USERMODE_PERCENT)

CPU usage per processor (%)

%

float

No

--

  • ((PROCESSOR_USER_TIME + PROCESSOR_SYSTEM_TIME) ÷ (PROCESSOR_USER_TIME + PROCESSOR_SYSTEM_TIME + PROCESSOR_IDLE_TIME + PROCESSOR_WAIT_TIME)) × 100

  • %sys column + %usr column when collecting results output by the sar command

Context Switches(PROCESSOR_CONTEXT_SWITCHES)

Number of times context switching was executed

AVG

ulong

Yes

HP-UX,

Linux

--

Context Switches/sec(PROCESSOR_CONTEXT_SWITCHES_PER_SECOND)

Frequency at which context switching was executed (number of times per second)

R

float

Yes

HP-UX,

Linux

PROCESSOR_CONTEXT_SWITCHES ÷ INTERVAL

Idle %(PROCESSOR_IDLE_PERCENT)

Percentage of time the processor was idle (%)

%

float

No

--

  • PROCESSOR_IDLE_TIME ÷ (PROCESSOR_USER_TIME + PROCESSOR_SYSTEM_TIME + PROCESSOR_IDLE_TIME + PROCESSOR_WAIT_TIME) × 100

  • %idle when collecting results output by the sar command

Idle Time(PROCESSOR_IDLE_TIME)

Time during which the processor was idle (seconds)

AVG

utime

Yes

--

--

Interrupts(PROCESSOR_INTERRUPTS)

Number of interrupts that occurred

AVG

ulong

Yes

HP-UX,

AIX

--

Interrupts/sec(PROCESSOR_INTERRUPTS_PER_SECOND)

Frequency at which interrupts occurred (number of times per second)

R

float

Yes

HP-UX,

AIX

PROCESSOR_INTERRUPTS / INTERVAL

Interval(INTERVAL)

Interval at which the CPU - Per Processor Detail (PI_CPUP) record was stored (seconds)

COPY

ulong

Yes

--

  • When delta values are not checked in real time, RECORD_TIME - Last-boot-time

  • Other cases, RECORD_TIME - Previous-record-time

Processor ID(LOGICAL_PROCESSOR_ID)

Processor identifier

COPY

string(12)

No

--

  • Does not apply when not collecting results output by the sar command.

  • cpu column when collecting results output by the sar command

Record Time(RECORD_TIME)

Time at which the record was created (Greenwich Mean Time)

COPY

time_t

No

--

--

Record Type(INPUT_RECORD_TYPE)

Record type. Always CPUP.

COPY

char(8)

No

--

--

Status(PROCESSOR_STATUS)

Processor status

COPY

string(12)

No

--

--

Sys Calls/sec(PROCESSOR_SYSTEM_CALLS_PER_SECOND)

Frequency at which system calls were issued (number of system calls per second)

R

float

Yes

HP-UX,

Linux

PROCESSOR_SYSTEM_CALLS ÷ INTERVAL

System %(PROCESSOR_SYSTEM_PERCENT)

Percentage of time the system ran in the kernel mode (%)

%

float

No

--

  • PROCESSOR_SYSTEM_TIME ÷ (PROCESSOR_USER_TIME + PROCESSOR_SYSTEM_TIME + PROCESSOR_IDLE_TIME + PROCESSOR_WAIT_TIME) × 100

  • %sys column when collecting results output by the sar command

System Calls(PROCESSOR_SYSTEM_CALLS)

Number of system calls that were issued

AVG

ulong

Yes

HP-UX,

Linux

--

System Time(PROCESSOR_SYSTEM_TIME)

Time during which the system ran in the kernel mode (seconds)

AVG

utime

Yes

--

--

Traps(PROCESSOR_TRAPS)

Number of traps that were executed

AVG

ulong

Yes

HP-UX,

AIX,

Linux

--

Traps/sec(PROCESSOR_TRAPS_PER_SECOND)

Frequency at which traps were executed (number of traps per second)

R

float

Yes

HP-UX,

AIX,

Linux

PROCESSOR_TRAPS ÷ INTERVAL

Type(PROCESSOR_TYPE)

Processor explanation

COPY

string(40)

No

--

--

Up Time(SYSTEM_UP_TIME)

Time elapsed since the last boot (seconds)

COPY

string(20)

No

--

RECORD_TIME - SYSTEM_BOOT_TIME

User %(PROCESSOR_USER_PERCENT)

Percentage of time the processor ran in the user mode (%)

%

float

No

--

  • PROCESSOR_USER_TIME ÷ (PROCESSOR_USER_TIME + PROCESSOR_SYSTEM_TIME + PROCESSOR_IDLE_TIME + PROCESSOR_WAIT_TIME) × 100

  • %usr column when collecting results output by the sar command

User Time(PROCESSOR_USER_TIME)

Time during which the processor ran in the user mode (seconds)

AVG

utime

Yes

--

--

Wait %(PROCESSOR_WAIT_PERCENT)

Percentage of time the processor was waiting for I/O (%)

%

float

No

Solaris

  • PROCESSOR_WAIT_TIME ÷ (PROCESSOR_USER_TIME + PROCESSOR_SYSTEM_TIME + PROCESSOR_IDLE_TIME + PROCESSOR_WAIT_TIME) × 100

  • %wio column when collecting results output by the sar command

Wait Time(PROCESSOR_WAIT_TIME)

Time during which the processor was waiting for I/O (seconds)

AVG

utime

Yes

Solaris

--

Legend:

Smry: Summary

Not sprtd in: Not supported in