Administering Resource Management in Oracle® Solaris 11.2

Exit Print View

Updated: July 2014

Setting Up Resource Management Task Map

The following task map provides a high-level overview of the steps to set up resource management on your system.

For Instructions
Identify the workloads on your system and categorize each workload by project.
Create project entries in either the /etc/project file, in the NIS map, or in the LDAP directory service.
Prioritize the workloads on your system.
Determine which applications are critical. These workloads might require preferential access to resources.
Refer to your business service goals.
Monitor real-time activity on your system.
Use performance tools to view the current resource consumption of workloads that are running on your system. You can then evaluate whether you must restrict access to a given resource or isolate particular workloads from other workloads.
Make temporary modifications to the workloads that are running on your system.
To determine which values can be altered, refer to the resource controls that are available in the Oracle Solaris system. You can update the values from the command line while the task or process is running.
Set resource controls and project attributes for every project entry in the project database or naming service project database.
Each project entry in the /etc/project file or the naming service project database can contain one or more resource controls or attributes. Resource controls constrain tasks and processes attached to that project. For each threshold value that is placed on a resource control, you can associate one or more actions to be taken when that value is reached.
You can set resource controls by using the command-line interface.
Place an upper bound on the resource consumption of physical memory by collections of processes attached to a project.
The resource cap enforcement daemon will enforce the physical memory resource cap defined for the project's rcap.max-rss attribute in the /etc/project file.
Create resource pool configurations.
Resource pools provide a way to partition system resources, such as processors, and maintain those partitions across reboots. You can add one project.pool attribute to each entry in the /etc/project file.
Make the fair share scheduler (FSS) your default system scheduler.
Ensure that all user processes in either a single CPU system or a processor set belong to the same scheduling class.
Activate the extended accounting facility to monitor and record resource consumption on a task or process basis.
Use extended accounting data to assess current resource controls and to plan capacity requirements for future workloads. Aggregate usage on a system-wide basis can be tracked. To obtain complete usage statistics for related workloads that span more than one system, the project name can be shared across several machines.
(Optional) If you need to make additional adjustments to your configuration, you can continue to alter the values from the command line. You can alter the values while the task or process is running.
Modifications to existing tasks can be applied on a temporary basis without restarting the project. Tune the values until you are satisfied with the performance. Then, update the current values in the /etc/project file or in the naming service project database.
(Optional) Capture extended accounting data.
Write extended accounting records for active processes and active tasks. The files that are produced can be used for planning, chargeback, and billing purposes. There is also a Practical Extraction and Report Language (Perl) interface to libexacct that enables you to develop customized reporting and extraction scripts.