Go to main content
Oracle® SuperCluster T5-8 Owner's Guide

Exit Print View

Updated: May 2016
 
 

Change CPU/Memory Allocations (Core Granularity)

Perform this procedure on each compute node to change its CPU and memory resource allocation at the core level.


Note - To find out if you can perform this procedure, see Supported Domain Configurations.

The tool makes these changes:

  • Automatically detects Root Domains.

  • Calculates the minimum and maximum resources for all domains, and only enables you to select valid quantities.

  • Presents viable memory capacities for you to select, based on your core allocations.

  • Modifies domain resources according to the choices you make.

  • (If needed) Stops nonprimary domains.

  • (If needed) Reboots the primary domain with new resources .

  • (If needed) Brings up nonprimary domains with new resources.

The examples in this procedure show a SuperCluster T5-8 compute node. The concepts in this procedure also apply to other SuperCluster models.

This table shows the allocation plan for this example (see Plan CPU and Memory Allocations).

Domain
Domain Type
Cores Before
Cores
After
Memory Before (GB)
Memory After (GB)
primary
Dedicated
16
16
256
256
ssccn2-dom1
Dedicated
16
22
256
384
ssccn2-dom2
Dedicated
32
32
512
512
ssccn2-dom3
Dedicated
16
8
256
64
ssccn2-dom4
Dedicated
16
18
256
320
ssccn2-dom5
Root
n/a
n/a
n/a
n/a
Unallocated
28
28
448
448
Total allocated resources
124
124
1536
1536
  1. Log in as superuser on the compute node's control domain.
  2. Activate any inactive domains using the ldm bind command.

    The tool does not continue if any inactive domains are present.

  3. Run osc-setcoremem to reconfigure the resources.

    Respond when prompted. Press Enter to select the default value.

    # /opt/oracle.supercluster/bin/osc-setcoremem
     
                                  osc-setcoremem
                        v1.0  built on Oct 29 2014 10:21:05
     
     
     Current Configuration: Full-Rack T5-8 SuperCluster
     
     +-------------------------+-------+--------+-----------+--- MINIMUM ----+
     | DOMAIN                  | CORES | MEM_GB |   TYPE    | CORES | MEM_GB |
     +-------------------------+-------+--------+-----------+-------+--------+
     | primary                 |    16 |    256 | Dedicated |     9 |     64 |
     | ssccn2-dom1             |    16 |    256 | Dedicated |     4 |     32 |
     | ssccn2-dom2             |    32 |    512 | Dedicated |     4 |     32 |
     | ssccn2-dom3             |    16 |    256 | Dedicated |     4 |     32 |
     | ssccn2-dom4             |    16 |    256 | Dedicated |     4 |     32 |
     | ssccn2-dom5             |     4 |     64 |   Root    |     4 |     64 |
     +-------------------------+-------+--------+-----------+-------+--------+
     | unallocated or parked   |    28 |    448 |    --     |    -- |   --   |
     +-------------------------+-------+--------+-----------+-------+--------+
     
     [Note] Following domains will be skipped in this session.
     
     Root Domains
     ------------
     ssccn2-dom5
     
     
     CPU allocation preference:
     
            1. Socket level
            2. Core level
     
     In case of Socket level granularity, proportional memory capacity is
      automatically selected for you.
     
     Choose Socket or Core level [S or C] C
     
     Step 1 of 2: Core count selection
     
     primary      : desired number of cores [min: 9, max: 80. default: 16] : <Enter>
                    you chose [16] cores for primary domain
     
     ssccn2-dom1  : desired number of cores [min: 4, max: 68. default: 16] : 22
                    you chose [22] cores for ssccn2-dom1 domain
     
     ssccn2-dom2  : desired number of cores [min: 4, max: 50. default: 32] : <Enter>
                    you chose [32] cores for ssccn2-dom2 domain
     
     ssccn2-dom3  : desired number of cores [min: 4, max: 22. default: 16] : 8
                    you chose [8] cores for ssccn2-dom3 domain
     
     ssccn2-dom4  : desired number of cores [min: 4, max: 18. default: 16] : 18
                    you chose [18] cores for ssccn2-dom4 domain
     
     New Configuration in progress after Core count selection:
     
     +-------------------------+-------+--------+-----------+--- MINIMUM ----+
     | DOMAIN                  | CORES | MEM_GB |   TYPE    | CORES | MEM_GB |
     +-------------------------+-------+--------+-----------+-------+--------+
     | primary                 |    16 |    256 | Dedicated |     9 |     64 |
     | ssccn2-dom1             |    22 |    256 | Dedicated |     4 |     96 |
     | ssccn2-dom2             |    32 |    512 | Dedicated |     4 |    128 |
     | ssccn2-dom3             |     8 |    256 | Dedicated |     4 |     32 |
     | ssccn2-dom4             |    18 |    256 | Dedicated |     4 |     80 |
     | *ssccn2-dom5            |     4 |     64 |   Root    |     4 |     64 |
     +-------------------------+-------+--------+-----------+-------+--------+
     | unallocated or parked   |    28 |    448 |    --     |    -- |   --   |
     +-------------------------+-------+--------+-----------+-------+--------+
     
     
     Step 2 of 2: Memory selection
     
     primary      : desired memory capacity in GB (must be 16 GB aligned) [min: 64, max: 1200. default: 256] : <Enter>
                    you chose [256 GB] memory for primary domain
     
     ssccn2-dom1  : desired memory capacity in GB (must be 16 GB aligned) [min: 96, max: 1040. default: 352] : 384
                    you chose [384 GB] memory for ssccn2-dom1 domain
     
     ssccn2-dom2  : desired memory capacity in GB (must be 16 GB aligned) [min: 128, max: 784. default: 512] : <Enter>
                    you chose [512 GB] memory for ssccn2-dom2 domain
     
     ssccn2-dom3  : desired memory capacity in GB (must be 16 GB aligned) [min: 32, max: 304. default: 128] : 64
                    you chose [64 GB] memory for ssccn2-dom3 domain
     
     ssccn2-dom4  : desired memory capacity in GB (must be 16 GB aligned) [min: 80, max: 320. default: 288] : 320
                    you chose [320 GB] memory for ssccn2-dom4 domain
     
     New Configuration in progress after Memory selection:
     
     +-------------------------+-------+--------+-----------+--- MINIMUM ----+
     | DOMAIN                  | CORES | MEM_GB |   TYPE    | CORES | MEM_GB |
     +-------------------------+-------+--------+-----------+-------+--------+
     | primary                 |    16 |    256 | Dedicated |     9 |     64 |
     | ssccn2-dom1             |    22 |    384 | Dedicated |     4 |     96 |
     | ssccn2-dom2             |    32 |    512 | Dedicated |     4 |    128 |
     | ssccn2-dom3             |     8 |     64 | Dedicated |     4 |     32 |
     | ssccn2-dom4             |    18 |    320 | Dedicated |     4 |     80 |
     | *ssccn2-dom5            |     4 |     64 |   Root    |     4 |     64 |
     +-------------------------+-------+--------+-----------+-------+--------+
     | unallocated or parked   |    28 |    448 |    --     |    -- |   --   |
     +-------------------------+-------+--------+-----------+-------+--------+
     
     
     The following domains will be stopped and restarted:
     
            ssccn2-dom4
            ssccn2-dom1
            ssccn2-dom3
     
     This configuration does not require rebooting the control domain.
     Do you want to proceed? Y/N : y
     
     All activity is being recorded in log file:
            /opt/oracle.supercluster/osc-setcoremem/log/osc-setcoremem_activity_10-29-2014_16:58:54.log
     
     Please wait while osc-setcoremem is setting up the new CPU, memory configuration.
     It may take a while. Please be patient and do not interrupt.
     
    0%    10    20    30    40    50    60    70    80    90   100%
    |-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|
    *=====*=====*=====*=====*=====*=====*=====*=====*=====*=====*
     
                    Task complete with no errors.
                    This concludes socket/core, memory reconfiguration.
                    You can continue using the system.
    
  4. Verify the new resource allocation.

    You can verify the resource allocation and check for possible osc-setcoremem errors in several ways:

  5. Repeat this procedure if you need to change resource allocations on another compute node.

Related Information