Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Oracle Solaris Zones, Oracle Solaris 10 Containers, and Resource Management Oracle Solaris 11 Express 11/10 |
Part I Oracle Solaris Resource Management
1. Introduction to Resource Management
2. Projects and Tasks (Overview)
3. Administering Projects and Tasks
4. Extended Accounting (Overview)
5. Administering Extended Accounting (Tasks)
6. Resource Controls (Overview)
7. Administering Resource Controls (Tasks)
8. Fair Share Scheduler (Overview)
Example 1: Two CPU-Bound Processes in Each Project
Example 2: No Competition Between Projects
Example 3: One Project Unable to Run
FSS and Processor Sets Examples
Combining FSS With Other Scheduling Classes
Setting the Scheduling Class for the System
Scheduling Class on a System with Zones Installed
9. Administering the Fair Share Scheduler (Tasks)
10. Physical Memory Control Using the Resource Capping Daemon (Overview)
11. Administering the Resource Capping Daemon (Tasks)
13. Creating and Administering Resource Pools (Tasks)
14. Resource Management Configuration Example
15. Introduction to Oracle Solaris Zones
16. Non-Global Zone Configuration (Overview)
17. Planning and Configuring Non-Global Zones (Tasks)
18. About Installing, Halting, Uninstalling, and Cloning Non-Global Zones (Overview)
19. Installing, Booting, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks)
20. Non-Global Zone Login (Overview)
21. Logging In to Non-Global Zones (Tasks)
22. Moving and Migrating Non-Global Zones (Tasks)
23. About Packages on an Oracle Solaris 11 Express System With Zones Installed
24. Oracle Solaris Zones Administration (Overview)
25. Administering Oracle Solaris Zones (Tasks)
26. Troubleshooting Miscellaneous Oracle Solaris Zones Problems
Part III Oracle Solaris 10 Zones
27. Introduction to Oracle Solaris 10 Zones
28. Assessing an Oracle Solaris 10 System and Creating an Archive
30. Configuring the solaris10 Branded Zone
31. Installing the solaris10 Branded Zone
32. Booting a Zone and Zone Migration
33. solaris10 Branded Zone Login and Post-Installation Configuration
Share allocation is not the same as utilization. A project that is allocated 50 percent of the CPU resources might average only a 20 percent CPU use. Moreover, shares serve to limit CPU usage only when there is competition from other projects. Regardless of how low a project's allocation is, it always receives 100 percent of the processing power if it is running alone on the system. Available CPU cycles are never wasted. They are distributed between projects.
The allocation of a small share to a busy workload might slow its performance. However, the workload is not prevented from completing its work if the system is not overloaded.