Monitoring Resource Usage
This section provides additional information that may help you to interpret the information that Performance Monitor provides that is related to the events reporting resource usage on host machines. These events are:
Event 150 (JVM Status).
Event 151 (Network Status).
Event 200 (Resources Per Process).
Event 300 (Host Resource Status).
Event 301 (Tuxedo "pq" Row).
Event 302 (Tuxedo "psr" Row).
These events report the usage of machine resources (CPU, memory, network, and so on). These events, except for Event 150 (JVM Status), make calls to external APIs (often specific to the operating system) to retrieve metric information. The monitored system sends each event at the sampling interval that is specified for that system.
This event applies only to web servers.
This event does not make calls to any operating system-specific API.
This event applies only to web servers.
For Event 151 (Network Status) the system launches a separate executable from Java that invokes the "netstat –n" command. On UNIX, the command runs in a separate shell. When the command finishes, the process ends. PeopleSoft does not run "netstat" with an interval argument.
Warning! On some platforms the "netstat" command can require up to a minute (or more) to finish. If the sampling interval is shorter than the time required for the command to complete, "netstat" commands will be running continuously.
This event applies to the application server and the Process Scheduler server.
The PeopleSoft system makes specific operating system calls to obtain metrics for %CPU that are used by the process, CPU time consumed, virtual memory size, and working set size. Operating systems have slightly different definitions for these quantities and different ways of reporting them. For instance, "working set" memory is a Windows term; "resident set" is the UNIX equivalent. PeopleSoft strives for consistency across platforms. For example, PeopleSoft expresses %CPU within a range from 0 to 100 on all machines even though some vendors scale to N*100% if multiple CPUs (N CPUs) exist.
Microsoft Windows and Linux compute one or more resources as an average of the two measurements at the beginning and end of a sampling interval. On these platforms, the Performance Monitor does not report an Event 200 (Resources Per Process) until the second sampling interval after you boot a server.
Process resource utilization is usually sampled by the operating system and written to a memory location. Windows writes to the registry, while UNIX writes to various files. The system reads the current values for the process, so events change only when the operating system updates the statistics. Most operating systems update these statistics at least once per second.
PeopleSoft obtains all information using lightweight, C++ programmatic APIs. No additional processes or shell commands are run.
Operating System |
Description |
---|---|
Windows |
Performance Monitor uses Performance Data Helper (PDH) to read registry counters. The information is identical to the Windows Performance Monitor tool. When multiple copies of a process, such as PSAPPSRV, are running, registry counters are assigned arbitrarily. For example, counter 1 and counter 2 can reverse their process assignment when a process reboots. Performance Monitor corrects for this.
|
AIX |
Performance Monitor reads the psinfo files, which is the same source of information that AIX uses for its "ps" command.
|
HPUX |
Performance Monitor reads pst_status using pstat_getproc.
|
Linux |
Performance Monitor reads ps information from /proc files.
|
Solaris |
Performance Monitor reads psinfo files, which is the same source of information that Solaris uses for its "ps" command.
|
OS/390 |
The only metric that is supported in the current release is Process Time. |
This event applies to the application server and the Process Scheduler server.
Performance Monitor makes specific operating system calls to obtain metrics for %CPU use on the host machine, %Memory use, and the hard page fault rate. Operating systems have slightly different definitions for these quantities, and they have different ways of reporting them. In most cases, PeopleSoft expresses %Memory use to reflect utilization of physical memory.
Performance Monitor programmatically queries the Tuxedo management information base (MIB) for total Jolt connections and total requests queued. All platforms compute one or more resources as an average of the two measurements at the beginning and end of a sampling interval. Performance Monitor does not report an Event 300 (Host Resource Status) until the second sampling interval after you boot the server.
Process resource utilization is usually sampled by the operating system and written to a memory location. Windows writes to the registry, while UNIX writes to various files. The system reads the current values for the process, so events change only when the operating system updates the statistics. Most operating systems update these statistics at least once per second.
PeopleSoft obtains all information using lightweight, C++ programmatic APIs. No additional processes or shell commands are run.
Operating System |
Description |
---|---|
Windows |
Performance Monitor uses Performance Data Helper (PDH) to read registry counters. The information is identical to the Windows Performance Monitor tool.
|
AIX |
Performance Monitor uses libperfstat API (a wrapper for knlist) to read kernel counters.
|
HPUX |
Performance Monitor uses pstat_getdyamic (pstat) to read kernel counters.
|
Linux |
Performance Monitor reads kernel statistics from files in /proc.
|
Solaris |
Performance Monitor uses the Kernel Statistics API (kstat) to read kernel counters.
|
OS/390 |
Performance Monitor uses the ERBSMFI and CVT APIs to report resource use on the logical partition. Higher priority jobs on other partitions can "steal" resources and not appear in these metrics.
|
This event applies to the application server and the Process Scheduler server.
The system programmatically queries the Tuxedo management information base (MIB) for the status of each queue.
This event applies to the application server and the Process Scheduler server.
The system programmatically queries the Tuxedo management information base (MIB) for the status of each server. Only PeopleSoft servers appear as Performance Monitor events; the BBL is not reported.