My Oracle Support Banner

Using PROCESSOR_GROUP_NAME to bind a database instance to CPUs or NUMA nodes on Linux (Doc ID 1585184.1)

Last updated on DECEMBER 31, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Linux x86-64
***Checked for relevance on 21-Jul-2017***

Purpose

This document provides a step-by-step guide for binding a database instance to a subset of a server's CPUs and memory, using Linux cgroups.  Cgroups provide a way to create a named set of CPUs and memory.  A database instance that is associated with this cgroup can only use its CPUs and memory.  

Using Linux cgroups, a DBA that is consolidating multiple database instances on a single server can

  1. Physically isolate database instances onto different CPUs
  2. Bind instances to specific NUMA nodes to improve performance on NUMA-based systems.

Scope

 

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Step 1 - Configuring the Linux cgroup
 Step 2 - Configuring the Database
 Best Practices
 Linux Cgroups vs Virtualization
 Support and Recommended Bug Fixes
 Bug Number
 Description
 Recommended Releases
 Bug 17013349
 MISC DEFECTS IN CGROUP CODE
 12.1.0.1 (fixed in 12.1.0.2)
 Additional Information
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.