Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
CPU shares allocation out of total (CPUShares)
This attribute reports the percentage of CPU shares allocated to the zone with respect to the total shares that are allocated to different zones sharing the resource pool.
If the resource pool facility is active, this value is reported for different zones sharing the resource pool. If the resource pool facility is inactive, the value is reported for all the zones on the system.
The system considers the CPU shares only when the scheduler of the project is Fair Share Scheduler (FSS). If the resource pool facility is active, FSS must be the scheduler of the resource pool. Otherwise, FSS is the default scheduler of the system. If the scheduler is not FSS, the CPU shares do not carry much meaning and hence this parameter is deactivated from monitoring. When the scheduler of the resource pool or the default scheduler of the system is FSS, and there is contention for CPU resources, the resource pool uses CPU shares to assign priority to the processes of the zones. This is very similar to the nice command in UNIX. Zones with large number of CPU shares are given higher priority over the zones with less number of CPU shares. For example, a zone with two CPU shares will use double CPU time than a zone with one CPU share; given that the resource pool has only two zones, there is contention for CPU resources.
The value for this parameter is calculated as follows: ((CPU shares of this zone) x 100) / (Total CPU shares)
The total shares is the sum of CPU shares of all the zones sharing the resource pool if the resource pool facility is active, or all the zones if the resource pool facility is inactive. When there is no process in the 'running' state from this zone, the zone does not get its share of the CPU resources, since it does not have any process to use the allocated resource capacity. Hence, the value of this parameter is, effectively, reported as zero, since the zone is not allocated any CPU time due to lack of contention. Also, the value of this parameter changes dynamically depending on the number of active zones at a given point in time. If the scheduler for the zone is not FSS, this parameter is deactivated. If the resource pool facility is active, the scheduler of the zone is the scheduler of resource pool; otherwise the scheduler of the zone is the default scheduler of the system.
