Dynamic CPU Scaling in Oracle Database 19c
From Oracle Database 19c (19.4) includes the ability to dynamically scale compute for Pluggable Databases (PDBs) up and down in response to workload demands using CPU min/max ranges. Scale-up and scale-down of compute resources available to a Pluggable Database can be configured to happen automatically, instantly, and dynamically without intervention.
[oracle@rac1 ~]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Wed Aug 19 19:43:08 2020
Version 19.4.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.4.0.0.0
SQL*Plus: Release 19.0.0.0.0 - Production on Wed Aug 19 19:43:08 2020
Version 19.4.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.4.0.0.0
SQL> show pdbs
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY YES
3 PDB READ WRITE YES
4 PDB1 READ WRITE YES
SQL>
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY YES
3 PDB READ WRITE YES
4 PDB1 READ WRITE YES
SQL>
SQL> show con_name
CON_NAME
------------------------------
CDB$ROOT
SQL>
CON_NAME
------------------------------
CDB$ROOT
SQL>
SQL> show parameter cpu
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
cpu_count integer 2
cpu_min_count string 2
parallel_threads_per_cpu integer 1
resource_manager_cpu_allocation integer 2
SQL>
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
cpu_count integer 2
cpu_min_count string 2
parallel_threads_per_cpu integer 1
resource_manager_cpu_allocation integer 2
SQL>
SQL> show parameter resource
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
resource_limit boolean TRUE
resource_manage_goldengate boolean FALSE
resource_manager_cpu_allocation integer 2
resource_manager_plan string
SQL>
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
resource_limit boolean TRUE
resource_manage_goldengate boolean FALSE
resource_manager_cpu_allocation integer 2
resource_manager_plan string
SQL>
SQL> alter session set container=pdb1;
Session altered.
Session altered.
SQL> connect sys/oracle@pdb1 as sysdba
Connected.
SQL>
Connected.
SQL>
SQL> show con_name
CON_NAME
---------
PDB1
SQL>
CON_NAME
---------
PDB1
SQL>
SQL> show parameter cpu
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
cpu_count integer 2
cpu_min_count string 2
parallel_threads_per_cpu integer 1
resource_manager_cpu_allocation integer 2
SQL>
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
cpu_count integer 2
cpu_min_count string 2
parallel_threads_per_cpu integer 1
resource_manager_cpu_allocation integer 2
SQL>
CPU min/max ranges work automatically, dynamically, and immediately, resulting in more effective use of compute resources in On-Premises and Cloud environments resulting in lower overall costs.
Please refer for more details:
https://blogs.oracle.com/database/dynamic-cpu-scaling-in-oracle-database-19c
Bug 28636532 - configure cdb resource plan, based on cpu_min and cpu_count (Doc ID 28636532.8)
No comments:
Post a Comment