Updated on 2024-09-05 GMT+08:00

Creating a Resource Pool

  1. Log in to the GaussDB(DWS) console.
  2. Choose Clusters. Click the name of a cluster.
  3. Choose Resource Management Configurations.
  4. Click Add Resource Pool.

    Up to 63 resource pools can be created.

  5. Configure the resource pool. For more information, see Table 1.

    Table 1 Resource pool parameters

    Parameter

    Description

    Default Value

    Name

    Resource pool name

    -

    CPU Resource (%)

    • CPU share: Percentage of CPU time that can be used by users associated with the current resource pool to execute jobs. The value is an integer ranging from 1 to 99.
    • CPU limit: Maximum percentage of CPU cores used by a database user in a resource pool. The value is an integer ranging from 0 to 100. 0 indicates no limit.
    NOTE:
    • The sum of the parameter values of all the resource pools cannot exceed 99%. If there is only one resource pool, the CPU share parameter does not take effect.
    • The CPU share parameter takes effect only when CPU contention occurs. For example, resource pools A and B are bound to CPU 1. If A and B are both running, the parameter takes effect. If there is only A running, the parameter does not take effect.
    • The sum of the CPU limits of all the resource pools cannot exceed 100%. The default value is 0.
    • The CPU limit is supported only by clusters of version 8.1.3 or later.

    -

    Memory Resource (%)

    Percentage of the memory that can be used by a resource pool.

    You can manage memory and query concurrency separately or jointly. Under joint management, jobs can be delivered only when both the memory and concurrency conditions are met.

    0 (not limited)

    Storage Resource (MB)

    Size of the available space for permanent tables.

    This parameter indicates the total tablespace of all DNs in a resource pool. Available space of a single DN = Configured value/Number of DNs.

    -1 (not limited)

    Complex Statement Concurrency

    Maximum number of concurrent queries in a resource pool.

    You can manage memory and query concurrency separately or jointly. Under joint management, jobs can be delivered only when both the memory and concurrency conditions are met.

    10

    Network Bandwidth Weight

    Weight for network scheduling. The value is an integer ranging from 1 to 2147483647. The default value is -1.

    CAUTION:

    Only clusters of 8.2.1 and later versions support the network bandwidth weight feature. DWS 3.0 clusters do not support this.

    -1 (not limited)

  6. Confirm the information and click OK.