6.2.10.1 chresourceprofile

Change a resource profile associated with a vault.

Purpose

The chresourceprofile command changes the attribute settings for an existing resource profile that is associated with an Exascale vault.

Syntax

chresourceprofile [vault-name/]resource-profile-name 
                  --attributes attribute=value[,attribute=value]...

Command Options

The options for the chresourceprofile command are:

  • resource-profile-name: Identifies the resource profile being changed.

  • vault-name: Identifies the vault that the resource profile is associated with.

    If not specified, then the current working directory is used to identify the vault.

  • --attributes: Specifies attributes to change. The following list outlines all of the available attributes:

    • iopsShareEF, iopsShareHC, iopsShareXT: Specifies the relative share of I/O bandwidth (IOPS) from extreme flash (EF), high capacity (HC), or extended (XT) storage that is available to each client associated with the resource profile. Each client’s share is relative to all other client shares associated with the corresponding media type. A higher share value implies higher priority. The range of valid values is 1-100, and the default value is 1.

    • iopsLimitEF, iopsLimitHC, iopsLimitXT: Specifies the upper limit of the I/O bandwidth (IOPS) from extreme flash (EF), high capacity (HC), or extended (XT) storage that is available to each client associated with the resource profile.

      Starting with Oracle Exadata System Software release 26.1.0, each value is a percentage with up to two decimal places. The range of valid values is 0.01-100, and the default value is 100 (effectively unlimited).

      Before Oracle Exadata System Software release 26.1.0, each value represents a fraction out of 10000. The range of valid values is 1-10000, and the default value is 10000 (effectively unlimited).

    • enableFlashCache, enableXrmemCache, enableFlashLog: Enables or disables use of the flash cache, XRMEM cache, or flash log for clients associated with the resource profile. Each value is Boolean, and the default is true (enabled).

    • flashCacheMin, xrmemCacheMin: Specifies the guaranteed minimum fraction of flash cache or XRMEM cache space available to each client associated with the resource profile.

      Starting with Oracle Exadata System Software release 26.1.0, each value is nominally a percentage with up to two decimal places. The range of valid values is 0-100, and the default value is 0 (no set minimum).

      Before Oracle Exadata System Software release 26.1.0, each value represents a fraction out of 10000. The range of valid values is 0-10000, and the default value is 0 (no set minimum).

      For each cache type, if the sum of all values across all resource profiles exceeds the maximum, then all the values are proportionally scaled down. Each value applies only when the corresponding cache is enabled in the resource profile (for example, enableFlashCache=true).

    • flashCacheSize / flashCacheMax, xrmemCacheSize / xrmemCacheMax: Specifies the maximum fraction of flash cache or XRMEM cache space available to each client associated with the resource profile. Starting with Oracle Exadata System Software release 26.1.0, the attribute names are flashCacheSize and xrmemCacheSize. Previously, they were flashCacheMax and xrmemCacheMax.

      Starting with Oracle Exadata System Software release 26.1.0, each value is nominally a percentage with up to two decimal places. The range of valid values is 0-100, and the default value is 100.

      Before Oracle Exadata System Software release 26.1.0, each value represents a fraction out of 10000. The range of valid values is 0-10000, and the default value is 10000.

      Each value applies only when the corresponding cache is enabled in the resource profile (for example, enableFlashCache=true).

Usage Notes

In addition to regular user-defined resource profiles, you can also define a system-reserved resource profile named $UNASSIGNED. All Exascale clients not explicitly associated with a resource profile are automatically governed by the $UNASSIGNED profile. The $UNASSIGNED resource profile contains only two modifiable attributes:

  • flashCacheSize / flashCacheMax: Specifies the maximum fraction of flash cache shared by clients associated with the $UNASSIGNED profile.

    Starting with Oracle Exadata System Software release 26.1.0, the attribute name is flashCacheSize. The value represents a percentage with up to two decimal places. The range of valid values is 0-100 and the default value is 100.

    Previously, the attribute name was flashCacheMax. The range of valid values was 0-10000 and the default value was 10000.

  • xrmemCacheSize / xrmemCacheMax: Specifies the maximum fraction of XRMEM cache shared by clients associated with the $UNASSIGNED profile.

    Starting with Oracle Exadata System Software release 26.1.0, the attribute name is xrmemCacheSize. The value represents a percentage with up to two decimal places. The range of valid values is 0-100 and the default value is 100.

    Previously, the attribute name was xrmemCacheMax. The range of valid values was 0-10000 and the default value was 10000.

All Exascale clients governed by the $UNASSIGNED profile share the corresponding cache resources. The behavior differs from regular resource profiles, where each application of the resource profile defines the resource allocation for one associated client.

You must create the $UNASSIGNED resource profile before you can modify it. If the $UNASSIGNED resource profile does not exist, the system automatically reserves 5% of each cache for unassigned Exascale clients, but unassigned clients share all of the unassigned cache space if more space is available.

Examples

Example 6-146 Change a Resource Profile

In this example, the iopsShareHC attribute is set to 11 for the silver resource profile in conjunction with the vault2 vault. 

@> chresourceprofile vault2/silver --attributes iopsShareHC=11

Example 6-147 Change a Resource Profile

In this example, the enableFlashLog attribute is set to false for the silver resource profile in conjunction with the vault2 vault. In this example, the vault association is not specified in the command but is derived from the current working directory in the ESCLI session. 

@vault2> chresourceprofile silver --attributes enableFlashLog=false

Related Topics

Parent topic: Resource Profile Management