CPU Over Commitment and Scheduling on Oracle VM Server 3.x
(Doc ID 1640862.1)
Last updated on MAY 22, 2024
Applies to:
Oracle VM - Version 3.0.1 and laterOracle Cloud Infrastructure - Version N/A and later
Private Cloud Appliance X5-2 Hardware - Version All Versions to All Versions [Release All Releases]
Linux x86-64
Purpose
Discuss CPU Over Commitment and Scheduling on Oracle VM Server 3.x.
Questions and Answers
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 |
| Questions and Answers |
| Intel Hyper-Threading |
| 1. Enable Intel Hyper-Threading? Or disable it? |
| 2. Two common mis-understandings after Intel Hyper-Threading is enabled. |
| NUMA (Non-Uniform Memory Access) |
| 1. Limit CPU scheduling on dom0 to logical CPUs in the first NUMA node. |
| 2. Single VM guest should not be assigned with vCPUs more than the number of logical CPUs in one NUMA node. |
| 3. CPU pinning on a VM guest within one NUMA node and avoid the first NUMA node. |
| 4. Any VM guest is not NUMA-aware |
| 5. Set CPU pining on VM guest before Live Migration |
| 6. Performance tuning if dom0_max_vcpus is less than 8 (OVS 3.4.1 and later) |
| Credit Scheduler |
| 1. Prefer adjusting vCPUs assignment of a VM guest to editing CPU scheduler parameters (e.g. Weight, Cap.) of a VM guest. |
| 2. Always keep dom0 with the only highest Weight. |
| References |