Processor utilization, Storage – HP ProLiant DL380 G5 Server User Manual
Page 36
•
Page Faults/sec—Rate at which the page faults occur in the executing threads within this process. A page fault
occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This does
not cause the page to be fetched from disk if it is on the standby list and already in main memory, or if it is in
use by another process with whom the page is shared.
•
% CPU Time—Percentage of elapsed time that all the threads of this process used the processor to execute
instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes
instructions, and a process is the object created when a program is run. Code executed to handle some
hardware interrupts and trap conditions are included in this count. On multi-processor machines, the maximum
value of the counter is 100 % times the number of processors.
•
% Privileged CPU Time—Percentage of elapsed time that the threads of the process have spent executing code
in privileged mode. When a Windows NT system service is called, the service often runs in privileged mode to
gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls
to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems,
Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of user
and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by
Windows NT on behalf of your application might be displayed in other subsystem processes in addition to the
privileged time in your process.
Processor Utilization
This window displays information about the system's processor utilization for different time intervals.
The system processor bar graphs display the percentage of total possible system processor utilization over the
specified period of time. A bar graph is displayed for every processor installed in the device. Use this graph to
determine if the system processor is a performance bottleneck.
Storage
Drive Array Controllers
This section displays general and status information about drive arrays. Select a drive array controller entry from the
Mass Storage list to display a submenu containing separate entries for Array Controller Information, Physical Drives,
Logical Drives, and storage system information. The following items display:
Array Controller Information
Select an array controller from the Mass Storage list to display information for the controller.
The following information displays for each controller:
•
Model—Displays the type of controller card.
•
Controller Status—Displays the array controller board status. The following values are valid:
•
OK—The array controller is operating properly.
•
General Failure—The array controller has failed.
•
Cable Problem—The array controller has a cable problem. Check all cables to the controller.
•
Powered Off—The array controller does not have power. Replace the controller and restore power to the
controller's slot.
•
Unknown—Indicates that the Storage Agents are unable to determine the status of the controller. You may
need to upgrade the Storage Agents.
•
Current Role—D
isplays the array controller's current role for duplexed array controllers. The following
values are valid:
•
Not Duplexed—This array controller is not duplexed.
•
Active—This duplexed array controller is the active controller.
•
Backup—This duplexed array controller is the backup controller.
•
Unknown—Indicates that the Storage Agents are unable to determine the role of the controller. You may
need to upgrade the Storage Agents.
•
Redundancy Model—Displays the redundancy type for the controller. The following values are valid:
•
Not Redundant—This array controller is not in a redundant configuration.
•
Driver Duplexing—The array controller is using a controller duplexing algorithm implemented exclusively in
the operating system driver.
•
Firmware Active/Standby—The array controller is using an active/standby algorithm implemented in the
controller firmware and the operating system driver.
Agent information 36