What is hardware BIOS configuration for performance?
In the world of high-stakes database performance, "Optimal Defaults" are usually just the starting point. To squeeze every microsecond of performance out of an Oracle Server X9-2 or Exadata node, you need to dive into the BIOS (UEFI) and align the hardware with your specific workload.
Here is the blueprint for configuring an Oracle x86 server for maximum performance.
On Oracle servers, you don't need a physical keyboard and monitor.
Via ILOM: Log in to the Oracle Integrated Lights Out Manager (ILOM) web interface, go to Host Management > Host Control, and select Next Boot Device: BIOS.
Via Console: Reboot the server and press F2 when the Oracle logo appears in the Remote Console.
By default, CPUs try to save power by "parking" cores or lowering clock speeds. For a database, this causes "latency spikes" as the CPU wakes up.
CPU P-State Control: Set to Max Performance. This prevents the CPU from down-clocking during quiet periods.
Energy Performance Bias: Change from "Balanced" to Performance. This tells the hardware to prioritize execution speed over power-bill efficiency.
Package C-State Control: Set to C0/C1 (or Disable deep sleep). This keeps the CPU in a high-readiness state, eliminating the "wake-up" delay when a query hits.
Hyper-Threading (Simultaneous Multithreading):
Enable (Default): Best for general-purpose workloads and massive parallel processing.
Disable: Often recommended for High-Performance Computing (HPC) or specific financial apps where "jitter" must be zero and predictable single-thread performance is king.
NUMA (Non-Uniform Memory Access):
Ensure this is Enabled. For Oracle Databases, NUMA allows the OS to keep data in the RAM sticks closest to the CPU core that needs it, cutting memory latency significantly.
NPS (Nodes Per Socket): On AMD-based Oracle servers (like X10M), set this to NPS1 or NPS4 depending on your workload density. NPS1 is generally best for large, monolithic databases.
If you are running Oracle VM Server or KVM, these settings are non-negotiable:
Intel VT-x / AMD-V: Must be Enabled to allow the hardware to assist the hypervisor.
Intel VT-d (Directed I/O): Enabled. This allows virtual machines to talk directly to PCIe hardware (like 100Gb NICs) with almost zero overhead.
SR-IOV: Enabled. This allows a single physical network card to appear as multiple "virtual" cards, improving I/O performance for multiple VMs.
| Menu Path | Setting | Goal |
| Advanced > CPU Power Mgmt | Energy Performance | Set to Performance |
| Advanced > CPU Power Mgmt | CPU C6 Report | Disabled (Prevents deep sleep) |
| Advanced > Processor | Hyper-Threading | Enabled (Usually) |
| Advanced > Memory | Memory Operating Speed | Auto (Ensures max supported MHz) |
| Advanced > PCI Subsystem | PCIe 64-bit Decode | Enabled (Required for modern GPUs/NVMe) |
If you ever get lost in the menus and the server starts behaving erratically, Oracle provides a safety net:
Press F9 within the BIOS to load Optimal Defaults.
This doesn't just reset to "factory"—it resets to a configuration Oracle has pre-validated for the best balance of stability and performance for the Oracle Database.
Configuring a BIOS for performance is about reducing variability. By disabling power-saving "sleep" modes and ensuring the CPU is always running at its peak frequency, you ensure that the first transaction of the day is just as fast as the millionth.