|
|
|
|
The overall CPU, disk and memory-related resources usage of the Hardware Node registered in Parallels Infrastructure Manager are displayed under the Overview subtab of the Resources tab on the Hardware Node dashboard.
The CPU and memory resources are explained in the following tables:
|
CPU |
Load |
The graphical presentation of the CPU load on the Node during the last minute and the percentage of the current Hardware Node utilization. |
|
|
The average number of active processes for the past 1, 5, and 15 minutes, respectively. Active processes can be running, i.e., currently executed by the CPU, or runnable, i.e., waiting in the run queue for the CPU. Value 0.00 means that the CPU is idle, 1.00 that the CPU is fully used. Value 2.00 denotes that the CPU load exceeds the nominal value by two times. |
|
Memory
|
Physical memory |
The percentage of the current Hardware Node utilization in terms of allocated memory. |
|
Swap Space |
The percentage of the current Hardware Node utilization in terms of allocated swap space. The bar is not displayed if swapping is not configured on the Node. |
|
|
RAM+Swap |
The total percentage of the current Hardware Node utilization in terms of both allocated memory and, if swapping is on, swap space. |
The information on the disk size usage in all the
partitions/
logical disks existing on your Physical Server is presented in the following tables (corresponding to the number of
partitions/
logical disks):
|
Column Name |
Description |
|
Resource |
The name of the resource. |
|
Used |
Consumed disk size (
|
|
Free |
Available disk size (
|
|
Total |
The total amount of disk size (
|
Note: If you need to free some of the resources, look at the CPU, Disk Space, Memory or Traffic screen showing which of the Containers hosted on the Node snatch the biggest piece of a corresponding resource. Then, depending on how important the operations run on these Containers are, you can suspend some of them. A suspended Container stays put, and so its processes and services do, to be later resumed from the checkpoint. Suspending Containers is a good method to disengage the Hardware Node recourses for a certain period of time or saving the state of current operations which can be quickly launched again afterwards. Remember, that repairing, restarting and reinstalling a suspended Container can change the saved state of the Container, so these actions are not recommended.
