Sunteți pe pagina 1din 14

1 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

The following is intended to outline our general product


direction. It is intended for information purposes only, and
may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions. The development, release, and timing of any
features or functionality described for Oracle's products
remains at the sole discretion of Oracle.

2 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.


Multitenant Database Resource
Management
Managing Shared Resources
Resource management in multitenant environment

Low Priority
Medium Priority
High Priority

4 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.


Managing Resources Between PDBs

• PDBs compete for shared resources


– CPU
– Parallel execution servers
– Sessions
– I/O
• Resource Manager enables policies that
prioritize/manage shared resources
– Set hard limits in consolidated environment
– ‘get what you pay for’

5 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.


Database Resource Manager
• In a CDB, Resource Manager can manage resources on two basic levels:
– CDB level - Resource Manager can manage the workloads for multiple PDBs
• Using CDB Resource Plan
– PDB level - Resource Manager can manage the workloads within each PDB
• Using PDB Resource Plan
• Resource Manager allocates the resources in two steps:
– It allocates a portion of the system's resources to each PDB (CDB Plan)
– In a specific PDB, it allocates a portion of system resources obtained in Step 1
to each session connected to the PDB (PDB Plan)
• Note: All activity in the root is automatically managed by Resource
Manager

6 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.


Database Resource Manager
• Using Database Resource Manager, you can:
– Specify that different PDBs should receive different shares of resources
– Limit the CPU usage of a particular PDB
– Limit the number of parallel execution servers that a particular PDB can use
– Limit the resource usage of different sessions connected to a single PDB
– Monitor the resource usage of PDBs
• Resources Managed:
– CPU
– Parallel execution servers
– Sessions
– Exadata I/O

7 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.


CDB Resource Plan
• A CDB resource plan allocates resources to PDBs according a set of
resource plan directives
• The resource plan directives control the allocation of:
– CPU
– Parallel execution servers
• The directives use a share value that you specify for each PDB
– A higher share value results in more resources
• You can also specify utilization limits for PDBs
– For CPU and parallel servers
– Can be used in conjunction with shares

8 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.


PDB Resource Plan
• A PDB resource plan determines how the resources allocated to a specific
PDB are allocated to consumer groups within that PDB
– A PDB resource plan is similar to a resource plan for a non-CDB
• You create directives for a PDB resource plan using the
CREATE_PLAN_DIRECTIVE procedure in the
DBMS_RESOURCE_MANAGER package

• You create directives for a CDB resource plan using the


CREATE_CDB_PLAN_DIRECTIVE procedure in the
DBMS_RESOURCE_MANAGER package

9 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.


An Example - CDB Resource Plan
“Utilization limits” are used to
Container Database enforce a hard limit on the
CPU/Parallel server usage for a
PDB
Sales Marketing Support “Shares” are used to specify how
50% min 25% min 25% min
100% max 75% max 75% max
CPU/Parallel Servers are
distributed between PDBs

CDB Resource Plan

PDB Shares Limit Guaranteed Maximum Maximum


Utilization Parallel CPU/Parallel CPU Parallel
Server Servers (share) (limit) Servers (limit)

Sales 2 2/4 = 50% 100% 100%

Marketing 1 75% 50% 1/4 = 25% 75% 50%

Support
10
1 75%
Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
50% 1/4 = 25% 75% 50%
An Example - CDB Resource Plan When all workloads are active,
they again share the CPU based
With Support and Marketing on their ratio of shares.
active, each gets an equal share

With a utilization limit of 75%, 100

SUPPORT is throttled, even 90


though CPU is available. 80

CPU 70
Utilization 60 Support (1 share)
50 Marketing (1 share)
Container Database 40 Sales (2 shares)
30

Sales Marketing Support 20


50% min 25% min 25% min 10
100% max 75% max 75% max 0

Utilization Limits provide clients consistent performance.


They also restrict their resource usage, based on what the client paid

11 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.


An Example - CDB Resource Plan
Configure a “default directive” that Container Database
automatically applies share and
utilization limits for subsequent
Sales Marketing Support
PDBs. 50% min 25% min 25% min
100% max 75% max 75% max
CDB Resource Plan
PDB Shares Limit Guaranteed Maximum Maximum
Utilization Parallel CPU/Parallel CPU Parallel
Server Servers (share) (limit) Servers (limit)

Default 1 50% 25% 1/n 50% 25%


Directive
Sales 2 2/4 = 50% 100% 100%
Marketing 1 75% 50% 1/4 = 25% 75% 50%
Support 1 75% 50% 1/4 = 25% 75% 50%
12 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
13 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
14 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

S-ar putea să vă placă și